Forum Discussion
Data from Table accessed through SQL database
It sounds like you aren't familiar with SQL; if I were you, I would go with the first method I mentioned above. It'll get you where you need to go without having to learn a new language. In fact, you can do most everything you'd want to do with the Query Editor GUI, rather than writing code.
However, if you want some more information on the SQL approach:
In that SQL code, "Employee" is the table name, and "ID/Name/Date" are all column names. It's a very small SQL statement that basically says:
From the "Employee" table, show me all of the data from the columns "ID", "Name", and "Date".
For more information on how to write some basic SQL, you can go here:
https://docs.microsoft.com/en-us/sql/t-sql/queries/select-transact-sql#examples
It sounds like you aren't familiar with SQL; if I were you, I would go with the first method I mentioned above. It'll get you where you need to go without having to learn a new language. In fact, you can do most everything you'd want to do with the Query Editor GUI, rather than writing code.
However, if you want some more information on the SQL approach:
In that SQL code, "Employee" is the table name, and "ID/Name/Date" are all column names. It's a very small SQL statement that basically says:
From the "Employee" table, show me all of the data from the columns "ID", "Name", and "Date".
For more information on how to write some basic SQL, you can go here:
https://docs.microsoft.com/en-us/sql/t-sql/queries/select-transact-sql#examples
Thank you. Youa re correct I am not familiar with SQL language. But I will try using the second one, because I am not sure if with the first method if I will have to do this every time I update the import with new rows of data from the SQL tables. :)
You will not have to repeat the steps when you refresh your data; when you perform steps in the Query Editor, it creates lines of code used to describe the end-result of what you're looking for; these are persistent across data refreshes. You can see these lines in the "Advanced Editor" in the Query Editor, if you're curious.
So if you remove those columns using the GUI method, with "Remove Other Columns", that change will stick no matter how many times you refresh your data, assuming you're still using that same PBIX file.
Either way, SQL is a fantastic language to know for anyone working with data. I'd recommend you get your feet wet with it anyway, and as a bonus, you will adding a valuable tool to your skillset that expands your job opportunities!
Thank you so very much for all the information SonnyChilds