Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
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:
Thanks,
-RK
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
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
17 | |
9 | |
8 | |
7 | |
7 |