I am receiving an error when connecting Power BI to Snowflake.
"Unable to Connect - We encountered an error while trying to connect. Details: "The server name should only be a host name".
I am putting our server in as:
https://xxxxxx.east-us-2.azure.snowflakecomputing.com
And I have put in the name of the Warehouse (compute) that I want to use to process the load:
PRD_BI_GENERAL_US_XS
I chose Import mode and left all the optional fields blank.
Try it without the "https://":
xxxxxx.east-us-2.azure.snowflakecomputing.com
Either from Power BI Desktop or Power BI service, the target Server when connecting to a Snowflake account has to be the hostname, therefore it doesn't need the HTTPS:// which instead is required to get to the Snowflake Account via Web UI.
An example would be: contoso.snowflakecomputing.com
Also, in order to successfully connect from Power BI you have to impersonate a Snowflake Role that is allowed 'Usage' permission on the Virtual Warehouse and the Database you want to get to. This can be done by having that specific Role as the Default Role for your Login.
Note that, since February 2021, Power BI Desktop supports Snowflake custom roles.
Reference:
https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-connect-snowflake#:~:text=To%20connect%20to%20a%20Snowflake,the%20box%20and%20select%20O
https://powerbi.microsoft.com/en-us/blog/power-bi-february-2021-feature-summary/#_Toc63074806
.
Related
im getting a error to refresh mi report in Power BI Service. Currently I can refresh the report locally however when I publish the report and then want to sync it to a gateway I get the following error:
I have this configuration in the new data source:
Finally i have this configuration in ODBC ( 64x):
Sometimes i get error of credentials but its impossible because y refresh the data with these credentials locally.
Thanks!
I try using different gateways, changue the configuration of the ODBC and Power BI Report. I have synchronized another report with the same gateway and it works correctly. Now when I try to link a second report to this same gateway I get the error.
I have SSMS installed on my laptop along with a localdb I created:
I am trying to create a connection with my localdb (in Power BI Service) and my local SQL db via my gateway but I keep getting an error. Here is a screenshot:
I am uploading a report from Power BI Report Builder. I am able to connect using the same credentials on Power BI Report Builder. However, when I enter the credentials on Power BI Service I get an error. Does anyone know why I am getting this error?
Try to install and use the normal SQL Server instead of LocalDB. When connecting to LocalDB, the necessary SQL Server infrastructure is automatically created and started, but I'm not sure that the Power BI Gateway supports that.
I'm trying to use the Direct Query feature in Power BI
It is working on Power BI Desktop, but when I publish it to Power BI online, it gives the error below.
The source database is Azure SQL Database with pricing tier Standard S0: 10 DTUs.
The Power BI license is Premium (I've also tried with Pro).
The firewall setting of the Azure SQL Database
The error:
Cannot load model
Couldn't load the model schema associated with this report. Make sure you have a connection to the server, and try again.
Please try again later or contact support. If you contact support, please provide these details.
Activity ID671fca94-b76e-4660-a944-dff3b06235b3
Request ID748c1fb6-d8c1-b1af-072a-ea49a79c6b64
Correlation ID862117fb-f595-4130-40be-f1d195fa7cbe
TimeSat Sep 18 2021 18:13:33 GMT+0200 (Central European Summer Time)
Service version13.0.16736.54
Client version2108.5.07549-train
Cluster URIhttps://wabi-europe-north-b-redirect.analysis.windows.net/
When you are using Azure SQL Database as a data source, you must provide credentials before the Power BI service shows the published report.
Follow the instructions to provide the credentials from this Microsoft document.
If credentials are not added error occurs when opening the published report or a dataset that is created with the DirectQuery connection.
I have designed a power bi report for a client using data set as his SQL Server database backup in my local system, and publish it on his provided power bi service account, now how do i connect this publish report with my client's local SQL server database?
In other words how my client be able to connect his local system's SQL database with this report?
You can use parameterized connection where you can store your local database access and client database access details, by using:
I have a MSSQL server on-prem and followed the steps from Microsofts Docs
in order to install the gateway.
Than i managed the gateway via manage gateways within power bi (cloud) and the test there worked and i got the green check.
Now the question how do i get the data from the gateway into a dataset? when i try to add a new dataset there and click on data bases i only get Azure SQL Database, Azure SQL Data Warehouse, SQL Server Analysis and Spark on Azure HDInsight but now sign of my fresh data gateway to my on-prem db.
Currently you can only access on premise SQL Server databases by building a model & publishing it to powerbi.com using the Power BI Desktop.
If you select "Import" as your connection option, Power BI will store the required data online. You will be able to query on that fixed data and work with it even when your connection to the on premises server is down. You can update your fixed dataset with new data if your connection is properly defined in your gateway.
If you select "DirectQuery" in your Power BI Desktop you will require an active connection to the On premises server for any reporting to work online. On the up side, it'll work on live data and will not store any data online.
When publishing, Power BI Desktop will try to match your connections used in your report to the ones defined in your gateways. If it can find a match, it'll automaticly link those up. It'll give you an informational message to let you know if this step succeeded after publishing. At the same time it'll add a dataset using the same data you used in the reports you just built.