Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
One of the tables in my data model is a Direct Query, underlying data is accessing an Azure SQL database.
I have set a timeout of 25 mins on PBI desktop. The table visual on PBI desktop takes ~13 mins to load. However, it times out on PBI Service.
How can I work to solve this issue?
Solved! Go to Solution.
Hi @bmk
To me DirectQuery should be used to return the data quickly. There is a timeout to ensure that resources are not exhausted.
I would recommend either making the query smaller with using the WHERE clause. Or import the data and refersh it on a schedule.
Hi @bmk
To me DirectQuery should be used to return the data quickly. There is a timeout to ensure that resources are not exhausted.
I would recommend either making the query smaller with using the WHERE clause. Or import the data and refersh it on a schedule.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.