ODBC Driver for Azure SQL

To install the Devart ODBC Driver for Azure SQL:

• Open the driver page and select the installer for your operating system.
• Download the installer and follow the prompts in the installation wizard.
• After successful installation, configure your Data Source Name (DSN) to start using the driver.

A DSN (Data Source Name) stores connection parameters so that applications can connect to Azure SQL without hardcoding credentials or settings. It simplifies and standardizes database connectivity across systems.

1. Open ODBC Administrator (Windows + R, then type odbcad32).
2. Choose 32-bit or 64-bit based on your app.
3. In the User/System DSN tab, click Add > Devart ODBC Driver for Azure SQL > Finish.
4. Fill in these settings:
   • Data Source Name: Friendly name (e.g., AzureSQLDSN).
   • Server: Azure SQL server address.
   • Database: Target database.
   • User ID/Password: SQL Server credentials.
5. Authenticate using the provided credentials.
6. Enable encryption by selecting Encrypt connection and setting Trust Server Certificate to No.
7. Click Test Connection to verify settings.

1. Register the ODBC driver in odbcinst.ini:

   [Devart ODBC Driver for SQL Azure]
   Driver = /opt/devart/odbc/sqlazure/libsqlazureodbc.so

2. Configure odbc.ini with:

   Driver = Devart ODBC Driver for SQL Azure
   Server = your-server.database.windows.net
   Database = your-database
   UID = your-username
   PWD = your-password
   Authentication = SQLServer
   Encrypt = True
   TrustServerCertificate = No

   Note

   Avoid storing passwords in plain text—use environment variables or secure key management.

3. Test the connection with:

   isql -v AzureSQLDSN your-username your-password

Error Description	Possible Causes	Solutions
Login/authentication errors	Incorrect username or password User not authorized on the Azure SQL Server	Double-check username and password for typos Verify that the login exists and has access to the target database If using Azure AD, ensure the correct Authentication mode is set in the DSN (AzureADPassword, AzureADIntegrated, etc.) Make sure your IP is allowed by the server firewall
Server, network, or firewall errors	Your machine’s IP address is not whitelisted in Azure SQL Server firewall settings Network port 1433 (used by Azure SQL) is blocked by local or corporate firewalls	Open Azure Portal > SQL Server > Firewalls and virtual networks and add the following: Your current IP Allow Azure services if needed Ensure that outbound traffic on port 1433 is allowed
Data source name or driver compatibility errors	Driver is not correctly installed or not registered Incorrect driver path in odbc.ini or odbcinst.ini	On Windows: Reinstall the Devart ODBC driver and confirm if it's listed in the ODBC Data Source Administrator On Linux/macOS: Verify the driver file path Check that the driver is correctly defined in odbcinst.ini: [Devart ODBC Driver for SQL Azure] Driver = /opt/devart/odbc/sqlazure/libsqlazureodbc.so
Encryption or certificate validation errors	Azure SQL requires SSL, but the DSN is not set up for encryption System does not trust Azure’s certificate authority	Ensure Encrypt = True and TrustServerCertificate = No in DSN Install trusted root certificates or set TrustServerCertificate = Yes (not recommended for production)

1. Enable connection pooling:

   • Set Pooling = True, Min Pool Size = 5, and Max Pool Size = 100.
   • Tune pool size based on usage.

2. Use parameterized queries

   • Example: SELECT * FROM Orders WHERE CustomerID = ?.
   • Prevents SQL injection and reuses execution plans.

3. Reduce network round trips:

   • Use batch queries or stored procedures.
   • Fetch only required columns.
   • Avoid frequent metadata lookups.

4. Optimize query execution plans:

   • Use Query Performance Insight in Azure Portal.
   • Add indexes and avoid functions on indexed columns.

5. Enable data compression:

   • Use UseUnicode = True and UseCompression = True in DSN.
   • Improves speed and reduces data size for large result sets.

The Devart ODBC Driver for Azure SQL provides a high-performance, standards-compliant interface for connecting to Azure SQL Database. It simplifies access from cloud-based or on-premises applications by offering consistent connectivity via the ODBC API. This functionality makes it easy for developers to work with Azure SQL just like a local database. The driver handles connection management, encryption, and authentication and supports modern cloud infrastructure requirements.

Devart’s ODBC driver is cross-platform, available for Windows, macOS, and Linux. Whether you're building apps in C++, Python, PHP, or BI tools, the ODBC driver allows you to integrate Azure SQL into diverse environments. Since the driver works on all major operating systems, you don’t have to write different code or use different database libraries per OS.

You can connect Power BI Desktop to Azure SQL via the Devart ODBC driver by selecting ODBC as the data source and choosing the preconfigured DSN. This enables dynamic querying and real-time dashboards based on your Azure SQL data. While SQL Server Management Studio (SSMS) uses native TDS protocol, the Devart ODBC driver is useful for third-party tools and scenarios where ODBC is required, e.g., reporting systems or cross-platform integrations.

The Devart ODBC Driver for Azure SQL offers broad support for standard SQL Server data types and ODBC API functions. However, some limitations may apply. For a full compatibility list, see this documentation.

Yes, the Devart ODBC Driver for Azure SQL supports SSL encryption (TLS 1.2+) to secure communication with Azure SQL.

To configure SSL, in your DSN or connection string, set Encrypt = True and TrustServerCertificate = No. This ensures traffic is encrypted and that the server’s certificate is validated.

SSH is generally not used with Azure SQL because it is a managed cloud service; SSL/TLS is the standard encryption method supported.