Azure Synapse Analytics
Catalog Synapse dedicated and serverless SQL pools with the SQL Server JDBC driver, with SQL lineage from views, procedures and query history.
Capabilities
| Capability | Support | Notes |
|---|---|---|
| Tables, views & columns | Supported | |
| Keys, constraints & indexes | Partial | |
| Procedures & functions | Supported | |
| Data lineage | Supported | |
| Lineage from query history | Supported | Statements collected from sys.dm_pdw_exec_requests. |
| 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://<workspace>.sql.azuresynapse.net:1433;databaseName=<pool>;encrypt=true; |
| Authentication |
Service principal (shared technical user) User principal (personal credentials, BYOC) Ephemeral credentials (asked at each run)
|
| Crawling strategy | SQL |
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 Synapse Analytics.
- A database user with
VIEW DEFINITIONon the pool. VIEW DATABASE STATEto read query history.db_datareaderfor data quality, profiling and Chat with your data.
Set up metadata crawling
- Create the connection to Azure Synapse Analytics on the agent (see Connection settings) and use Test to verify it.
- Create or open the system that represents Azure Synapse Analytics 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.
Lineage from query history
The agent can periodically extract executed statements from Azure Synapse Analytics and send them to Blindata, where the SQL lineage engine turns them into dataflows. See the ready-made extraction query in Scheduling and statements extraction.
Related guides
- Microsoft SQL Server: same driver and extraction queries
- Metadata import with interface tables
- Data quality probes
- Automated SQL lineage
- Scheduling agent jobs