Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
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
Good Morning,
Quick question, whats the best/preferred way to use DirectQuery? Do you use it direct into your visuals, or build Summary Tables off of it which you then use in your visuals?
In addition, measures based off which (direct/summary) offer faster value?
Thank you
Hi @BugmanJ
Direct Query Advanatge and use case:
DirectQuery in Power BI offers the greatest benefits in the following scenarios:
Some general implications and limitations of using DirectQuery follow:
If data changes, you must refresh to show the latest data.
If data changes, there's no guarantee of consistency between visuals.
You must refresh in Power BI Desktop to reflect schema changes.
A limit of 1 million rows can return on any query
ou can't change a model from import to DirectQuery mode.
It is recommended to use when you have large dataset but slow down the performance because everytime when you hit the slicer of select any visual data complete query go back to orginal data source and fetch the result. You dont have full capacity f calculation also. Few DAX supported in Direct query mode.
If hope this post helps you please give kudos and accept it as a solution!
Thanks
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.
| User | Count |
|---|---|
| 48 | |
| 44 | |
| 40 | |
| 18 | |
| 18 |
| User | Count |
|---|---|
| 69 | |
| 69 | |
| 32 | |
| 32 | |
| 32 |