DQC

Connection to Azure SQL

To connect an Azure SQL database to the DQC Platform, you’ll need to provide connection credentials for a read-only SQL user and whitelist the platform’s IP. This guide explains all necessary steps.

Add an Azure SQL connector

To begin:

  1. Go to the Data Connectors screen

  2. Click the Azure SQL Server button

  3. Enter the connection parameters described below

Select Azure SQL to begin configuring your database connection

📝 Required connection information

Field

Example

Description

Name

OurBestDatabase

Custom name to identify your connection

User

sqladmin

A SQL user with read-only permissions

Password

{your password here}

Password for the SQL user

Host

dbmsname.database.windows.net

Usually in the format: <name>.database.windows.net

Port

1433

Default port for Azure SQL

Database name

our_best_database

Name of the target database within the Azure SQL instance

.

User configuration & permissions

We recommend creating a dedicated SQL user for the DQC Platform connection with read-only access.

✅ Dedicated, Minimal-Privilege User

  • Avoid using admin or shared credentials

  • Create a user specific to DQC Platform access

🔒 Assign Read-Only Role

In SQL Server Management Studio or via script, grant the following:

USE [your_database];
CREATE USER [dqcreader] FOR LOGIN [dqcreader_login];
ALTER ROLE db_datareader ADD MEMBER [dqcreader];

Whitelist the DQC Platform IP Address

To allow inbound connections from the DQC Platform, whitelist the following static IP in your Azure SQL firewall settings:

3.123.94.228

Troubleshooting

When DQC cannot connect to Azure SQL or load its tables, it shows the reason with a short fix and links to this section. Look up the beginning of the message:

Message in DQC

Likely cause

Fix

Login to Azure SQL failed. …

Wrong user name or password, or SQL authentication is not enabled on the server

Check user name and password; the user must be a SQL authentication user

Database … cannot be opened. …

Wrong database name, or the user has no access to that database

Check the database name and create the user in that database

The firewall of … does not allow DQC. …

The Azure SQL server firewall blocks the DQC IP address

Add the DQC Platform IP address to the server firewall

Connection to …:… not possible. …

DQC cannot reach the server: wrong host or port, or a firewall or security group blocks the DQC IP address

Check host and port, whitelist the DQC Platform IP address, or connect through the DQC Proxy

The TLS certificate of … could not be verified. …

The server presents a self-signed certificate or one that does not match the host name

Use a certificate of a trusted certificate authority that matches the host name

Unable to connect to Azure SQL database. Reason: …

Another ODBC error; the reason names it

Act on the reason, or contact support with the full message

Could not connect to the data source. Check the connection details …

DQC could not classify the error of the connection test

Check every field of the form, the network access and the permissions described above

Table not accessible anymore …

The table was renamed, moved or deleted, or the user lost access to it after the last sync

Restore the table or the access, then resync the connector

Technical user is not allowed to create virtual tables …

Virtual tables need temporary tables in the source

Allow the user to create temporary tables, or do not use virtual tables on this connector

  • Synchronization failed: when a sync cannot connect, the connector shows Failed on the Data sources screen and the badge links to this section. Edit the connector and click Load tables or Save: DQC tests the connection again and shows the current reason.

  • Tables missing from the table list: DQC lists only tables of the configured schema (default dbo) that the user can read. Assign the read-only role (see Assign Read-Only Role).

  • Still stuck? Write to support@dqc.ai with the connector name, the time of the attempt and the full message.

💡 Notes