Hello @SQLGeek ,
Thanks for posting the question and welcome to Microsoft Q & A .
It was difficult to troubleshoot a performance issue without accessing the data , but below are few pointers .
- Please check things like unhealthy indexes, bad statistics, running a heavy query etc.I would recommend starting with a scale up, a rebuild of the cluster Columnstore Index on the fact table with a largeRC/static50 and a stats update with fullscan. Read more here .
- check the cluster Columnstore Index health of the fact table (how many compressed row groups and how big they are)?
- What is that we are filtering on , Is it a “simple” select * from fact_table where ColumnX = ‘value”? Or does the query have a more complex structure
Scaled at DW100, only have a single compute resource to handle all 60 distributions in the table, translating that to a SQL environment, they are running 60 queries in parallel on a single vm. At that low a level, each of those queries is getting a very small resource allocation.
Please let me know how it goes .
Thanks Himanshu
Please do consider to click on "Accept Answer" and "Up-vote" on the post that helps you, as it can be beneficial to other community members