Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi @ERing I hope this helps. Thank You!!
In Power BI, when you are using DirectQuery mode, the data model relies on the underlying database's capabilities for processing and transforming data. This means that certain data transformations and type changes that you can perform in Power Query's Power BI Desktop may not be supported when using DirectQuery.
DirectQuery mode is designed to leverage the processing capabilities of the data source, like Snowflake in your case, rather than pulling all the data into the Power BI engine. As a result, some data transformations, especially those that involve changing data types or complex transformations, might not be possible to perform directly in Power Query when using DirectQuery.
Thank you for the detailed explanation.
What considerations should be made when deciding between import and direct query? I find myself using direct query frequently, because my tables often have over 3 million rows, however I find myself challenged by the limitations in direct query.
Should I be using import? At what point is it necessary to use direct query rather than import?
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 19 | |
| 10 | |
| 9 | |
| 7 | |
| 6 |