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 am just starting with Power BI and have been using Native Database Queries to use pre-determined SQL for my data source. This allows for some data transformation (select only certain fields from a table, rename fields to be end-user friendly).
1. Are there any particular reasons that I should be using Native Database Queries when using the get data wizard?
2. Is there a way to easily get back to the SQL entry screen once the data has been imported?
Solved! Go to Solution.
1. I would anticipate that Native Database Queries are more efficient. If you use something like a SQL SELECT statement and only select certain columns, then the unselected data never makes it to the Desktop for example. Otherwise, my understanding is that it will grab everything and then as part of the query whittle down columns based upon query steps.
2. Edit Queries, select query, in Source step, click the gear icon.
1. I would anticipate that Native Database Queries are more efficient. If you use something like a SQL SELECT statement and only select certain columns, then the unselected data never makes it to the Desktop for example. Otherwise, my understanding is that it will grab everything and then as part of the query whittle down columns based upon query steps.
2. Edit Queries, select query, in Source step, click the gear icon.
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 |
| User | Count |
|---|---|
| 11 | |
| 9 | |
| 5 | |
| 4 | |
| 4 |