Forum Discussion
Power BI Dataverse TDS Endpoint SQL Timeout
Hi,
Does anybody know if there is a limitation or timeout on TDS endpoint sql in Power BI for dataverse? I'm getting the below error but there's only 90k rows ish. There is a few joins on it, but I wanted to understand why it was timing out or any limitations.
It loads absolutely fine locally on the desktop but as soon as it refreshes in the service it times out.
Timeout expired. The timeout period elapsed prior to completion of the operation
Thanks
Hi lherbert501
Service has stricter timeouts 2–5 mins per query where TDS endpoint is not optimized for complex joins. Desktop works because it runs locally and no service timeout. Also row count (90k) is not the issue.
You can avoid joins in Power BI and push logic into Dataverse views, reducing columns, using Dataverse connector instead of TDS SQL, importing tables separately and model relationships in Power BI.
TDS endpoint is meant for light querying and not heavy reporting workloads.
2 Replies
Hi lherbert501
Service has stricter timeouts 2–5 mins per query where TDS endpoint is not optimized for complex joins. Desktop works because it runs locally and no service timeout. Also row count (90k) is not the issue.
You can avoid joins in Power BI and push logic into Dataverse views, reducing columns, using Dataverse connector instead of TDS SQL, importing tables separately and model relationships in Power BI.
TDS endpoint is meant for light querying and not heavy reporting workloads.
I think the svc’s just stoppin’ at the fixed 30s TDS gate, so tuck the heavy joins into a tiny DV view n’ let PBI pull only the lite shape—if it still breaks, swap to the std Dataverse conn to bypass TDS.
