Azure SQL Database
Supported
Relational databases
Catalog Azure SQL Database and Azure SQL Managed Instance with the Microsoft SQL Server JDBC driver.
Capabilities
| Capability | Support | Notes |
|---|---|---|
| Tables, views & columns | Supported | |
| Keys, constraints & indexes | Supported | |
| Procedures & functions | Supported | |
| Data lineage | Supported | |
| Lineage from query history | Partial | Query Store is enabled by default on Azure SQL Database. |
| Business glossary links | Supported | |
| Data quality probes | Supported | |
| Data profiling | Supported | |
| Data classification | Supported | |
| Chat with your data | Supported |
Connection settings
Create the connection on the Blindata Agent from Settings > Agents > Connections with the connection wizard, choosing Microsoft SQL Server in the technology step.
| Driver class | com.microsoft.sqlserver.jdbc.SQLServerDriver |
|---|---|
| JDBC URL | jdbc:sqlserver://myserver.database.windows.net:1433;databaseName=mydb;encrypt=true; |
| Authentication |
Service principal (shared technical user) User principal (personal credentials, BYOC) Ephemeral credentials (asked at each run)
|
| Crawling strategy | SQL |
Connection properties
| Property | Description |
|---|---|
authentication | ActiveDirectoryPassword, ActiveDirectoryServicePrincipal or SqlPassword. |
The driver is included in the Blindata Agent: no installation is needed. Driver properties can be added under Advanced settings in the connection wizard.
Prerequisites & permissions
- A Blindata Agent installed with network access to Azure SQL Database.
- A contained database user (SQL or Microsoft Entra ID) in each database to document.
VIEW DEFINITIONto read view and procedure bodies,VIEW DATABASE STATEfor Query Store.db_datareaderfor data quality, profiling and Chat with your data.
Set up metadata crawling
- Create the connection to Azure SQL Database on the agent (see Connection settings) and use Test to verify it.
- Create or open the system that represents Azure SQL Database in the catalog and link it to the connection.
- In the CRAWLING tab add a crawling job with strategy SQL.
- Run a TEST to check the number of extracted objects, then RUN or schedule the job.
The job options and the column aliases of every extraction query are described in the Generic JDBC reference.
Related guides
- Microsoft SQL Server: same driver and extraction queries
- Metadata import with interface tables
- Data quality probes
- Automated SQL lineage
- Scheduling agent jobs