Forum Discussion
SQL Azure Import Data Refresh
- 9 years ago
I finally figured it out: the connection FQDN included the word "secure".
This won't allow server-side refresh: <database name>.database.secure.windows.net.
This will allow servers-side refresh: <database name>.database.windows.net
Both FQDNs seem to work otherwise. The 'secure' setting was used to enable auditing, but I don't think it is required anymore.
Problem solved. Thanks everyone.
-Jeff
Hi Lydia, I can confirm that the personal gateway works. But I cannot as your screenshot indicates. I am going to try a brand clean install on another machine, and connect to Azure SQL with a minimal PBIX file.
This is what I see with the personal gateway installed and working:
Hi jdunmall,
Based on your desktop, you combine Azure SQL database data source and web data source in a dataset, when you remove the data source from the dataset, do you require gateway? In addition, I don't use Windows credential, I use database credential.
Thanks,
Lydia Zhang
- jdunmall9 years agoAdvocate I
I finally figured it out: the connection FQDN included the word "secure".
This won't allow server-side refresh: <database name>.database.secure.windows.net.
This will allow servers-side refresh: <database name>.database.windows.net
Both FQDNs seem to work otherwise. The 'secure' setting was used to enable auditing, but I don't think it is required anymore.
Problem solved. Thanks everyone.
-Jeff
- jdunmall9 years agoAdvocate I
Yes Lydia, I've tried a basic PBIX with only one Azure SQL database connection. Same problem.
I have since gone through the process of creating a brand new Azure SQL database, and it works! I can refresh directly through PowerBI. Now I need to track down why it doesn't work with the "real" Azure SQL DB. But some progress.
I'll post back when I work out what is special about the one that isn't working.
Thank you again for your help.
- jdunmall9 years agoAdvocate I
Update: I have confirmed Power BI requires a personal gateway in our main azure subscription with a brand new SQL database and test database. In a separate test subscription with exactly the same Azure SQL setup, a personal gateway is not required.
There is something specific about our subscription that is causing this problem. I'm at the end of my ideas to troubleshoot, and so we are opening a Microsoft ticket.