Azure Synapse Collected Data
This page lists what Sifflet imports from your Azure Synapse dedicated SQL pools once you connect Sifflet to Azure Synapse.
Imported Assets
Sifflet imports the following assets into the Data Catalog, for each schema in the scope of the source:
- Tables
- Views
Collected Metadata
Sifflet reads the following metadata of tables and views from the dedicated SQL pool:
| Asset | Metadata |
|---|---|
| Tables and views | Name, schema, database, and asset type (table or view) |
| Columns | Name, data type, nullability, and maximum length |
Lineage
Sifflet doesn't build lineage between assets inside Azure Synapse.
Sifflet links your Synapse tables to the assets of other integrations that read from them, such as Power BI datasets: you see which Power BI reports depend on a Synapse table.
Data Freshness
Sifflet refreshes Synapse metadata on the schedule of the source: see Integrations Management for the default frequency and how to change it. New tables, views, and columns appear in Sifflet after the next refresh.
Limitations
- Only dedicated SQL pools are supported: Sifflet doesn't connect to serverless SQL pools or Apache Spark pools.
- Sifflet doesn't build lineage between Synapse assets, and doesn't collect usage or query history.
Data Exposure
Sifflet reads row-level data from Synapse only on demand, for data preview and to display failing rows of a monitor, and doesn't store it. Sifflet doesn't collect query history from Synapse, so the asset update history isn't available. See Security for details on the data Sifflet accesses and stores.
Updated about 2 hours ago

