Honestly, DirectQuery is for the rich!
@marcorus26K followers
12,921 views #Honestly #powerbi #directquery
10 Comments
Comments from the original post on X (Twitter)

@ehansalytics
Everyone that talks to their Snowflake sales rep will be told DQ is the best when working with Snowflake data. Yea, it can perform decently, but still pales in comparison to import. The main reason is money flies from your bank account to Snowflakes with each visual query processed. 💸💸💸💸
18 likes

@MicahDail
I do prefer avoiding DQ, but just about every model we have has DQ with aggregates. I can't get away!
3 likes

@marcorus
You are certainly aware of pros/cons. Many people don’t, so I tried to simplify the message. 😎
2 likes

@dtdickler
Honestly, with live connections to SSAS multi-dimensional model cubes you do not have all these performance headaches.
1 like

@marcorus
Long live to Multidimensional!
4 likes

@ThomasIvar62
When you cannot import data into Power BI with an acceptable time window then DQ can be interesting. I have not met that scenario so far.
1 like

@MathewWestwood
You always talk sense Marco and always appreciated 👏
1 like

@NYCGuy1463
What if you get a fresh set of information every month across multiple tables ? DQ allows the new data to just flow in.

@marcorus
I don't get the point. You refresh every month. Unless you want to spend more for each query, of course. Your choice.
1 like

@dinesh35004871
Please share your opinion on direct lake by comparing with import mode from performance point of view.
