Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. 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.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
13 | |
13 | |
10 | |
8 | |
7 |
User | Count |
---|---|
17 | |
10 | |
7 | |
6 | |
6 |