Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

July 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more

Reply
Ritesh_Air
Post Patron
Post Patron

DirectQuery or Import for Snowflake

Hello,

We got Snowflake as our new datasource. On Day 1, I thought I should use DirectQuery but I am already running into limitations from the get go.

So bit of a general question:

  1. DirectQuery or Import for Snowflake?
  2. These limitations make DirectQuery not an attractive proposition. Any advice why should we use DirectQuery?

 

Ritesh_Air_0-1660922379903.png

 

 

Ritesh_Air_1-1660922395706.png

 

 

Thanks,

-RK

 

1 REPLY 1
Vijay_A_Verma
Most Valuable Professional
Most Valuable Professional

Though everything is context specific but in Direct Query, many DAX and M language functions don't work. And also, every interaction like filter etc. (i.e. every query) is sent to Snowflake. So, if you have many users who are sending requests to Snowflake and Snowflake charges you for it use. So, cost can increase very much compared to Import. In case of import, once you import the data resides in Power BI service till you refresh again. So, every request from user is not sent to Snowflake but to Power BI service.

There are other factors as well in considering DQ/Import.. A good comparison of DQ vs Import is here - https://www.phdata.io/blog/import-vs-direct-query-power-bi/ 

 

👍 It's been a pleasure to help you | Help Hours: 11 AM to 9 PM (UTC+05:30)

How to get your questions answered quickly -- How to provide sample data

Helpful resources

Announcements
Fabric Data Days is here Carousel

Data Days 2026

Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.