The new Data Catalog feature includes several new tables which can be useful for understanding underlying connections in Tableau Server. A non-exhaustive list:
There are also hist_ tables for each of these, along with _events tables. These tables are all generated in the process of Data Catalog discovering and tracking what assets it has processed into the GraphQL database for Catalog.
On the database_assets table, the source_type and source_id can be used to join to the workbooks or datasources table. It's not clear that these can be linked to a data_connections record, though, which is what would be needed to determine which connection used the assets in question, though. There also seems to be no link between columns as found in databases in general, and how they're used in a given workbook or data source. Nor is there any link yet between a view and it's data connection(s).
On the whole, I tend to think we're probably better off just incorporating some basic fields from data_quality_indicators into this, and offloading the heavy lifting for what-uses-what logic to Data Catalog.
The new Data Catalog feature includes several new tables which can be useful for understanding underlying connections in Tableau Server. A non-exhaustive list:
column_assets table_assets database_assets data_quality_indicators
There are also hist_ tables for each of these, along with _events tables. These tables are all generated in the process of Data Catalog discovering and tracking what assets it has processed into the GraphQL database for Catalog.
On the database_assets table, the source_type and source_id can be used to join to the workbooks or datasources table. It's not clear that these can be linked to a data_connections record, though, which is what would be needed to determine which connection used the assets in question, though. There also seems to be no link between columns as found in databases in general, and how they're used in a given workbook or data source. Nor is there any link yet between a view and it's data connection(s).
On the whole, I tend to think we're probably better off just incorporating some basic fields from data_quality_indicators into this, and offloading the heavy lifting for what-uses-what logic to Data Catalog.