DP-203 · Question #82
You are designing a partition strategy for a fact table in an Azure Synapse Analytics dedicated SQL pool. The table has the following specifications: - Contain sales data for 20,000 products. - Use…
The correct answer is B. 240. Each partition should have around 1 millions records. Dedication SQL pools already have 60 We have the formula: Records/(Partitions60)= 1 million Partitions= Records/(1 million 60) Partitions= 2.4 x 1,000,000,000/(1,000,000 * 60) = 40 Note: Having too many partitions can reduce…
Question
You are designing a partition strategy for a fact table in an Azure Synapse Analytics dedicated SQL pool. The table has the following specifications:
- Contain sales data for 20,000 products.
- Use hash distribution on a column named ProduclID,
- Contain 2.4 billion records for the years 20l9 and 2020.
Which number of partition ranges provides optimal compression and performance of the clustered columnstore index?
Options
- A40
- B240
- C400
- D2,400
How the community answered
(35 responses)- A11% (4)
- B80% (28)
- C6% (2)
- D3% (1)
Explanation
Each partition should have around 1 millions records. Dedication SQL pools already have 60 We have the formula: Records/(Partitions*60)= 1 million Partitions= Records/(1 million * 60) Partitions= 2.4 x 1,000,000,000/(1,000,000 * 60) = 40 Note: Having too many partitions can reduce the effectiveness of clustered columnstore indexes if each partition has fewer than 1 million rows. Dedicated SQL pools automatically partition your data into 60 databases. So, if you create a table with 100 partitions, the result will be 6000 https://docs.microsoft.com/en-us/azure/synapse-analytics/sql/best-practices-dedicated-sql-pool
Topics
Community Discussion
No community discussion yet for this question.