Azure SQL Managed Instance is the intelligent, scalable cloud database service that combines the broadest SQL Server database engine compatibility with all the benefits of a fully managed and evergreen platform as a service. SQL Managed Instance has near 100% compatibility with the latest SQL Server (Enterprise Edition) database engine, providing a native virtual network (VNet) implementation that addresses common security concerns, and a business model favorable for existing SQL Server customers. SQL Managed Instance allows existing SQL Server customers to lift and shift their on-premises applications to the cloud with minimal application and database changes. At the same time, SQL Managed Instance preserves all PaaS capabilities (automatic patching and version updates, automated backups, high availability) that drastically reduce management overhead and TCO.
For more details on the database, please see the Microsoft official documentation.
As of Strategy 2021 Update 3, you can now retrieve data from Azure SQL Managed Instance with Strategy.
Azure SQL Managed Instance has near 100% compatibility with the latest SQL Server database. As such, you can use the Microsoft Server connector in Strategy 2021 to connect to SQL Managed Instance. When hovering over the connector, the tooltip indicated that Azure SQL Managed Instance is supported, as shown below.

Internal tests indicates that the performance of the ODBC driver is much better than that of the JDBC driver. Strategy suggests using the ODBC driver over the JDBC driver. The following table outlines the result of a data fetch performance test.
show this help message and exit | show this help message and exit | show this help message and exit |






The ODBC connection string can be:
DRIVER={Strategy ODBC Driver for SQL Server Wire Protocol}; hostname={host}; Port={port}; Database={db}; AuthenticationMethod=1; EncryptionMethod=1; ValidateServerCertificate=0;

JDBC;DRIVER={com.Strategy.jdbc.sqlserver.SQLServerDriver};URL= {jdbc:Strategy:sqlserver://{host}:{port};DatabaseName={db};EncryptionMethod=SSL;ValidateServerCertificate=false;fetchTWFSasTime=TRUE;}