This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowThe Fabric community is upgrading! Read all of the details including the timeline and what you can expect. Learn more
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 !!
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
| User | Count |
|---|---|
| 24 | |
| 22 | |
| 20 | |
| 18 | |
| 14 |
| User | Count |
|---|---|
| 44 | |
| 37 | |
| 23 | |
| 21 | |
| 20 |