Loading video...

Video Failed to Load

Go Home

Honestly, DirectQuery is for the rich! Set your expectations right. You cannot optimize DirectQuery to perform like Import mode. #Honestly #powerbi #directquery

12,921 views • 1 year ago •via X (Twitter)

10 Comments

Ed Hansberry - MVP's profile picture
Ed Hansberry - MVP1 year ago

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

Micah Dail's profile picture
Micah Dail1 year ago

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

Marco Russo's profile picture
Marco Russo1 year ago

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

Daniel Dickler's profile picture
Daniel Dickler1 year ago

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

Marco Russo's profile picture
Marco Russo1 year ago

Long live to Multidimensional!

Thomas Ivarsson's profile picture
Thomas Ivarsson1 year ago

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.

Mathew Westwood's profile picture
Mathew Westwood1 year ago

You always talk sense Marco and always appreciated 👏

NYCGuy1463's profile picture
NYCGuy14631 year ago

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

Marco Russo's profile picture
Marco Russo1 year ago

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

dinesh's profile picture
dinesh1 year ago

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

Related Videos