Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowTry your skills in the Power BI Dataviz World Championship! Round one ends June 26. Join now
I Need to use direct query for my reports that make my impossible to us power query,so i dont can format my data the right way ,so i try to use the sql server native query option,but i see on the documentation that its can have the limitashon,first that its will not have query folding,second its can have security issues (i don't expierence this issue), so my question is if i am doing all my querys in the native sql and i dont need the power query editor, if its a good idea to use the sql native query option,for my now its looks amazing its works even faster from the regular dataverse connector,and i can make the querys much better and format the datat much better,but maybe when i will have large data its will get slower,so if anyone can help my to make a decision if to use native query and explain what its will be the bad side and the good side from it, i will appreciate!
@mf123 Not sure I 100% understand the ask. First, it is generally optimal to push data transformation as far back as possible. So, if you need to do data transformation then do it by creating a SQL View for example and then just connect directly to that view. You can do a query that executes a SQL query. That is perfectly fine as long as you don't need to do any additional data transformation within the query itself because at that point you can't preserve query folding.
thanks for your answer,my problem is that i use dataverse so i can't create views
| User | Count |
|---|---|
| 22 | |
| 21 | |
| 20 | |
| 20 | |
| 11 |
| User | Count |
|---|---|
| 62 | |
| 55 | |
| 46 | |
| 45 | |
| 34 |