This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register 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.
Check out the April 2026 Power BI update to learn about new features.
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 |
|---|---|
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |