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

To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.

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
Super User
Super User

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
September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.

Top Kudoed Authors