Forum Discussion
DAX Studio - Server Timing error against F SKU
Hi Dblain2,
Thank you for reaching out to the Microsoft Fabric Forum Community.
If the issue still persists, I’d recommend raising a support ticket with Microsoft. The support team can look into the backend and provide more in-depth assistance tailored to your environment.https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
If this solution helped, please consider marking the response as accepted and giving it a thumbs-up so others can benefit as well.
Best regards,
Prasanna Kumar
Hi Dblain2,
Thanks for reaching out to the Microsoft Fabric Forum Community.
Possible workarounds I can Think off are,
Use XMLA Endpoint Instead: Connect to the workspace using the XMLA endpoint and use View Metrics in DAX Studio. This is often more stable for F SKU environments.
Test with Higher SKU (F64+): If you're on a lower-tier F SKU (e.g., F2–F32), try testing on an F64 or higher, which more closely mirrors Premium capacities and may support richer telemetry.
If this helped, please mark the response as the accepted solution and give it a thumbs-up so others can benefit too.
Best regards,
Prasanna Kumar
Thanks for you response! I believe I'm already connected via the XMLA endpoint. I believe thats the only way to connected to a Premium workspace via DAX Studio. I was able to get View Metrics to run, however this isn't what i'm looking to do. I am looking to test query timings to do some testing.
I've tried multiple different scenarios. I've tried on an F64 and F32. I've also tried on a workspace that I'm the admin of. I've also toggled the large vs small semantic model setting. None have allowed me to connect. I am able to connect via SSMS, but this experice is subpar compared to DAX Studio.
- Deku
Super User
Have you tried updating Dax studio to the latest version?
Unfortunately, I was already on the latest version. I tried going back a version but still no luck. I'll probably try going back a couple more versions today to see if I can get it going. It's curious that others aren't having this issue. It almost seems like there is a setting in the workspace or admin portal that might be preventing this. That's a complete guess though. To this point, I've not seen any other post of people having issues similar to mine so it must not be a broad scale problem...
Update - I tried multiple older versions of DAX studio and it did not resolve the issue.
