I have data in Azure SQL DB, I used import (not directQuery) while making reports in Power BI Desktop, when i published them on Power BI web, I don't see option to schedule data Referesh for the reports.
I have tried installing on-premises data gateway but it fails to configure.
Related
We have recently implemented Azure Synapse Workspace into our reporting landscape. The purpose of this Synapse Workspace is to store Dynamics data to be reported on by Power BI. We were using the Data Export Services mechanism to move data from Dynamics to Azure SQL Server and report from there but MS have deprecated DES and we now use Synapse as the substitute.
I have found, and this happens 50% of the time during working hours, that when I amend a Power BI report and the Power Query element re-evaluates itself, the re-evaluation seeks an update from the source - which is the Azure Synapse Workspace, the re-evaluation fails. I get an 'Operating system error code 12'. The error message is below with sensitive text scrubed.
Click this to show the error message received
Having Googled the error, it tells me a read (i.e. a Power BI refresh/re-evaluation) cannot take place against the Synapse Workspace if Synapse is updated being by Dynamics during the same time.
Is this correct? I can't believe MS would devise a DES replacement that cannot be read from if it is being updated from the source. The source (Dynamics) will be updated throughout the working day and so this would mean that no one can read from Synapse during the working day.
I'm wondering if further configuration is required within Synapse to allow reads.
If you can confirm what I'm facing is correct and/or advise me on how to remedy this it will be greatly appreciated.
Thanks.
I'm stumped on what to do. I have verified that when the Power BI report fails its refresh/re-evaluation the failing entity has actually been updated in the Synapse Workspace's CSV file. So the Google explanation seems to be correct.
Our current web application uses Azure SQL Database. We need to create a scheduled process for importing/exporting data from a SQL database in Azure Virtual Machine to Azure SQl database. And also provide ability to trigger manually.
Currently we have manual scripts with Linked server which needs to be run on both servers.
What are the best options available for clean import/Export data automation (scheduled or manual)? for e.g. Secure Connection between servers, Tools or Applications (other than SSIS)
Could someone please provide guidance.
Thank you,
Vamshi
You can use SQL Data Sync tool to sync data between an Azure SQL Server VM and an Azure SQL database. The sync can be done manually or scheduled with a frequency of days, hours, minutes and seconds.
Of course, you can also use SSIS for that purpose. But you may see intermittent connection failures that can substantially impact data loads.
You can use Azure Data Factory to connect to Azure SQL VM and Azure SQL Database and using the copy data tool export/import data from one to the other, and vice versa.
Disclaimer: not a developer, but an analyst looking for solutions
I currently have a DOMO dashboard ready, am looking to port/replicate it on Power BI for another set of users who have the rest of their dashboards on Power BI. Is there a way I can do this?
Found a link with regard to having a writeback connector, is this the right one to go about doing it?:
https://domohelp.domo.com/hc/en-us/articles/360063090013-Power-BI-Writeback-Connector
Another similar(?) question on this forum:
https://community.powerbi.com/t5/Developer/Custom-Connector-with-Token-Refresh/m-p/2320423
The worst case scenario given to me, is to recreate the dashboard directly with the data source used in the DOMO dashboard (which I find the most intuitive as an analyst).
I could be trying to do the opposite of what the user here was trying to do from Power BI to DOMO:
Power BI to DOMO
I see there being two options for your use case, you can move the data out of Domo to Azure / Power BI via the Power BI Write-back Connector, which you have already identified, this can be automated and scheduled like a regular Domo process and is all managed and contained within the Domo UI, or, you could retain your data in Domo and have Power BI query it directly by via the ODBC Data Driver.
The ODBC driver setup creates a DSN (Data Source Name) on your machine which references your Domo instance, allowing you to create queries against Domo directly. You can then connect Power BI to that ODBC Connection.
I believe the visualisations would need to be re-created manually, I'm not aware of a tool that would let you port these across.
I am importing data from SQL DW to Power Bi using SQL server authentication credentials.
I read in this Microsoft Doc that VNets can be used as Data gateways for various Power BI Data sources. Can this be applied here? Transfer of data from Synapse SQL DW to Power BI service will always happen through public internet or can it happen through VNets also?
I am new with these services, so my question could be silly!
Yes you can connect through public internet as well as from private vnet(data gateway).
Virtual network data gateways allows import or direct query datasets to connect to data services within an Azure VNet without the need of an on-premises data gateway.
as per the doc you are following VNet data gateways will support connectivity to the following Azure data services:
1.Azure SQL
2.Azure Synapse Analytics
3.Azure Data Explorer (Kusto)
4.Azure Table Storage
5.Azure Blob Storage
6.Azure HDInsight (Spark)
7.Azure Data Lake (Gen2)
8.Cosmos DB
Note:The The virtual network (VNet) data gateway is still in preview. and Virtual network data gateways is a premium-only feature, and will be available only in Power BI Premium workspaces and Premium Per User (PPU) for public preview. However, licensing requirements might change when VNet data gateways become generally available.
Reference
Create virtual network data gateways
I'd like to allow a Power BI report to access a single azure SQL database in such a way that it could allow for cleaner deployment/replication across multiple products. As of now, I manually provide the reports with a read only SQL login, but having to do this each time a new report is created would be sub-optimal.
Is there any way to integrate Power BI with Azure's MSI, or anything of the sort to allow for smoother deployment?
You can connect to the Azure SQL database through the PowerBI online service and then publish this as a 'content pack'.
Then you can use the PowerBI Service Connector to access the dataset without creds.