![]() Unfortunately, the error message, although accurate, is not as explicit as it could be. This error occurs when the account running the website can not connect to the database. In case of error, a complete error message is displayed: $conn.ConnectionString = "Server=(local) Database=Sample Integrated Security=True " $conn.Open() If this option is not possible (for example with a Windows Server Core Edition), it is still possible to use PowerShell: $conn = New-Object Open the created file ⇒ A window to enter the login information opens.I then put in the default values, in order to connect to the correct Azure SQL Database.There are many cases where we want to verify that the connection string used by an application is valid (in production of course □). ![]() Whilst in the Power Query Editor I then created 2 Parameters, one for the Server Name and another for the Database Name I then created a second table, which runs the TSQL command this is to ensure that not only could I get back the relevant server name, but that I am indeed not masking the results for this blog post (Honesty is the BEST policy ) NOTE: As you can see above my colour has the name of “Black-Svr1_DW” I created my Power BI Report, where I first connected to the Azure SQL Database and imported the SalesLT.Products table from Server1_DW Then in order to ensure that I was looking at the different servers, I updated the Products table so that for the Colour Black it was changed to “Black-Svr1_DW” and “Black_Svr2_DW” Creating the Power BI Report As part of the installation I installed the Adventure Works databases Not only was this very quick to complete, it was also extremely cheap with it costing $6.99 AUD per month for me test my solution. What I did in order to test the changing of the connection strings is I created 2 Sample Azure SQL databases. ![]() ![]() One thing to take note of, is that this currently only works on Imported data sources and not DirectQuery or LiveConnection Data Preparation ![]() I would need to ensure that I have an On-Premise Gateway configured for my Disaster recovery servers, and once again I could change the connection strings. If I was looking for disaster recovery options, this too could work.This would work particularly well if I am deploying reports from Dev (Development environment) to Test (Testing environment ) to Prod (Production environment).I would be able to change the underlying data source connection without having to redeploy my Power BI desktop file. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |