This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hi,
One of the most important design decisions you have to make when building PBIX or SSAS 2016 Tabular models is whether you import/load the data from the source system into memory or if you use Direct Query mode and let the source system process the report queries. If your source system is a supported Direct Query data source, and the model you're building is more than a quick pilot/POC, then you have to know and evaluate the many trade-offs such as performance, data freshness, modeling features supported, maintenance, etc.
I tried to summarize many of these factors and considerations in a Word document available for download from my blog:
SSAS 2016 Tabular: In-Memory vs Direct Query
Note: This document should not be viewed as comprehensive and per my blog more testing and research on the DAX restrictions/limitations and the SQL query plans generated across source systems is needed.
-Brett
Hi @Brettp761,
Thanks for your sharing. ![]()
Best Regards,
Qiuyun Yu
Great document. Thanks for sharing your work and reflexions !!
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 37 | |
| 32 | |
| 27 | |
| 24 | |
| 17 |
| User | Count |
|---|---|
| 70 | |
| 50 | |
| 31 | |
| 26 | |
| 22 |