Video wird geladen...
Video konnte nicht geladen werden
Honestly, DirectQuery is for the rich! Set your expectations right. You cannot optimize DirectQuery to perform like Import mode. #Honestly #powerbi #directquery
12,921 Aufrufe • vor 1 Jahr •via X (Twitter)
10 Kommentare

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. 💸💸💸💸

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

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

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

Long live to Multidimensional!

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.

You always talk sense Marco and always appreciated 👏

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

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

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