You have an Azure Synapse Analytics dedicated SQL pool named Pool1. Pool1 contains a fact table named Table1.
You need to identify the extent of the data skew in Table1.
What should you do in Synapse Studio?
You have an Azure Synapse Analytics dedicated SQL pool named Pool1. Pool1 contains a fact table named Table1.
You need to identify the extent of the data skew in Table1.
What should you do in Synapse Studio?
To identify the extent of data skew in a table within an Azure Synapse Analytics dedicated SQL pool, you should connect to the built-in pool and query sys.dm_pdw_nodes_db_partition_stats. This Dynamic Management View (DMV) provides detailed information about the distribution of data across the nodes and partitions, which is essential for identifying data skew. Running this query will give insights into the distribution of data and help pinpoint any imbalances present. The views available in the built-in pool are specifically designed to provide such detailed metrics and diagnostics.
I think it is B , same question in the previous pages
It is indeed B: https://learn.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-distribute#determine-if-the-table-has-data-skew
...no. Please read better the resource: "Create the view dbo.vTableSizes that is shown in the Tables overview article." the article --> https://learn.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-overview#table-size-queries The cited view indeed uses dm_pdw_nodes_db_partition_stats, so A is the correct answer, not B.
"However, using DBCC commands can be quite limiting. Dynamic management views (DMVs) show more detail than DBCC commands."
REPETED,B is correct
Answere B Topic 4 #36 and #38
B is correct
Explanation: To identify the extent of data skew in a table within an Azure Synapse Analytics dedicated SQL pool, the DBCC PDW_SHOWSPACEUSED command is most appropriate. This command provides information about space usage and data distribution, which can help identify skew. You need to connect to the specific pool (Pool1) to run this command.
The built in pool is serverless, we cannot use those A's DMV is not supported by serverless pools, https://learn.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-db-partition-stats-transact-sql?toc=%2Fazure%2Fsynapse-analytics%2Fsql-data-warehouse%2Ftoc.json&bc=%2Fazure%2Fsynapse-analytics%2Fsql-data-warehouse%2Fbreadcrumb%2Ftoc.json&view=azure-sqldw-latest&preserve-view=true