Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. 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
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |
| User | Count |
|---|---|
| 7 | |
| 5 | |
| 5 | |
| 5 | |
| 4 |