Forum Discussion
Post ProdigyPower BI Dataverse TDS Endpoint SQL Timeout
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.
Super UserHi 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.