Forum Discussion
SQL Azure Import Data Refresh
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 jdunmall,
Based on my test, when we connect to Azure SQL database via Import mode in Power BI Desktop, after we publish the Power BI Desktop file to Power BI Service, no gateway is required if we want to set schedule refresh for the dataset, you can check the example below.
In your scenario, do you combine other on-premises data source and Azure SQL database data source in a single Power BI Desktop file(PBIX file)? If that is the case, when you publish the PBIX file to Power BI Service, personal gateway is required when setting schedule refresh.
In addition, when you firstly connect to Azure SQL database via DirectQuery mode in Power BI Desktop, you are able to switch it to Import mode, however, it will not allow you switch back to DirectQuery mode from Import mode. You would need to recreate the PBIX file if you want to use DirectQuery mode.
Thanks,
Lydia Zhang
I do see one thing different here - you are using Windows credentials to access SQL Azure and I am using database credentials. Is that a problem?