Forum Discussion
DAX Studio and SQL profiler
agree with smpa01 - you should focus on the Power Query part, not on DAX Studio. Also be aware that you are dangerously close to hitting the hard limit of 300 minutes - after that any dataset or dataflow refresh on the service will be killed. You want to get your duration down to not more than 2.5 hrs (to be on the safe side). Keep in mind that your refresh is blocking a renderer for the entire time, which means that renderer is not available for other users either.
Read about bootstrapping for incremental refresh partitions.
I completely agree lbendlin and smpa01 . Just ran the view again in SQLServer. Took 23 minutes. But we are planning to add an index. The main issue for now is that I get that SQL Profiler error. So I can't get insights in why it takes so long.
Furthermore I will dive into bootstrapping. Never heard of it 🙂
Thnx, is on my read list. Is there something else then SQL Profiler to get insight in why refreshing takes so long?
Use SSMS and examine the actual query execution plan. It will even suggest indexes for you.