Prerequisites for adding an Azure Synapse source
Azure Synapse is an analytics service built on SQL Server, with two options: serverless (on-demand) SQL pool and dedicated SQL pool. To connect to Azure Synapse, you need existing Microsoft Entra ID or Microsoft SQL Server accounts. These accounts need to have the permissions listed in the following table to access databases, schemas, and tables within your Synapse workspace. For more information, see Synapse Database Objects and Microsoft Azure documentation.
1 The Storage Blob Data Reader permission is needed on the blob storage services containing external tables. Microsoft SQL Server credentials (login and password) cannot feature or read data from external tables.
2 For authorization with Microsoft Entra ID for Synapse workspaces on a server-less pool, you will be able to view all catalog assets in Lineage (as nodes) and table-view relationships (as edges), but not table-table relationships (as edges). Also, the utilization metrics in Catalog will only show the count of reads, because writes are handled outside of the Synapse (updating the files in the blog store).
Add Azure Synapse credentials
To monitor Azure Synapse Analytics in Validio, add valid credentials for either Microsoft Entra ID or Microsoft SQL Server. Refer to the following credential parameters tables. For more information, see About Credentials. To add a credential for Azure Synapse,- Navigate to Credentials and click + New credential.
- Under Namespace, select a namespace where the resources will be created.
- For Credential Type, select Microsoft Entra ID Credential or Microsoft SQL Server Credential.
- Fill in the Configuration parameters for the credential. Refer to the relevant credential parameters table.
- (Optional) Click Test credential to validate that Validio can successfully access the configured account. If validation fails, check that you provided the correct parameter values.
- (Optional) Check Use for catalog and schema checks to automatically discover assets from this credential and add them to the Catalog page.
- Click Create credential.
Microsoft Entra ID credential parameters
Microsoft SQL Server credential parameters
Add an Azure Synapse source
To add a source for Azure Synapse,- Navigate to Sources and click + New source.
- Under Source type, select Azure Synapse.
- Under Config,
- Select the valid Credential or create a new credential to authenticate your connection to the data warehouse.
-
- You have two options for specifying the dataset and tables to monitor:
- Select an existing table — Enter the Database, Schema, and Table to specify where the data comes from. Selecting more than one table will create a new source for each table. Refer to the Source Configuration Parameters table.
- Use Custom SQL — Write a valid SQL query to specify the tables to monitor.
- You have two options for specifying the dataset and tables to monitor:
- Set the Polling schedule, which is how frequently the validators on the source will check for changes.
- Under Schema, click Continue to automatically infer the schema fields from the tables you selected. If you select many tables, this operation can take a few minutes to complete.
- Under Source details,
- Add Tags to help group related sources or to use for routing notifications.
- Add an Owner who will be the contact for incident notifications.
- Assign a Priority, which indicates the importance of incidents detected on this source.
- Click Continue to create the source. Source names are generated automatically and will be displayed when the source creation completes. If there are more than 5 sources, you will see the names for the first five and a count of the remaining sources.
Source configuration parameters
Synapse database objects
Validio queries specific database objects to populate Catalog and Lineage pages after the source is added.Catalog
Catalog
sys.databasessys.schemassys.objectssys.tablessys.columnssys.extended_propertiessys.typesINFORMATION_SCHEMA.TABLES
Lineage
Lineage
sys.dm_exec_requests_historysys.dm_pdw_exec_requestssys.dm_pdw_exec_sessions