The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Hi,
I'm having problem using DAX Studio with datasets in Premium capacity workspaces. The connection is unstable - it gets disconnected every now and then, but the biggest issue is using server timings. It only works with fast queries ( < 2 seconds), if I try to use it for anything that takes longer, it gets switched off after the query is executed. Has anyone else experience this?
Solved! Go to Solution.
Ok, I think I've got it partially solved and it looks like it can be fixed on DAX Studio side. In Options-->Timeouts you can modify the times for Server Timings End Event Timeout and Trace Startup Timeout. Once I've increased it from original 30 seconds to 90, I can collect statistics on longer running queries. So far I was mostly working with AAS models and never had to change these settings. Maybe Power BI Premium connection isn't as responsive.
The unstable connection is still an issue, however it's something I can live with as it doesn't happen too often.
Thanks for sharing this, I was experiencing a similar issue and it seems like increasing the timeout values is helping!
Ok, I think I've got it partially solved and it looks like it can be fixed on DAX Studio side. In Options-->Timeouts you can modify the times for Server Timings End Event Timeout and Trace Startup Timeout. Once I've increased it from original 30 seconds to 90, I can collect statistics on longer running queries. So far I was mostly working with AAS models and never had to change these settings. Maybe Power BI Premium connection isn't as responsive.
The unstable connection is still an issue, however it's something I can live with as it doesn't happen too often.
No, SSMS works perfectly fine.
You could try raising a ticket but since DAX Studio is a third party app they probably won't be enthusiastic about this.
That is highly unusual. Do you have the same issue with SSMS?