I don't understand the difference between Analysis Services Connector and Personal Gateway. It seems to me that they have the same role.
Both the tools are synonymous, SSAS Connector(Analysis services connector) is an old tool which has been replaced by Power BI gateway. I was not able to refresh my multidimensional analysis cubes using SSAS connector and once I used power BI gateway I was able to get refreshed data in power BI. In Fact power BI gateway has some major enhancements like SSAS connector does not support multidimensional cubes, while the new power BI personal gateway has the ability to connect your on premise multidimensional cubes to Power BI. you can have more insights on these links
http://biinsight.com/power-bi-and-ssas-multidimensional/
http://whitepages.unlimitedviz.com/2015/07/power-bi-personal-gateway/comment-page-1/
As per this link, Microsoft recommends to upgrade Analysis service connector with Power BI Gateway as it gives 2X performance improvements.
Related
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
My company wants to speed up the process of delivering reports. Internally, we have a team of 12 people working on building reports. The company is a large company with over 10,000 employees. We're asked to work on adhoc reports quite frequently, but it takes us on average 1-2 weeks to deliver these reports. Senior Execs have said that the time to deliver is too slow. An external consulting firm came into to do some discovery work and they have advised that business users should have access to the Azure Data Warehouse, so that they can directly build models in Azure Analysis services and Power BI.
The design that they have suggested is as follows:
Load data from SAP, into the Azure Data Warehouse directly.
Build our data models in the Azure DW - this means all the transformation work is done directly in Azure DW (Staging, Cleansing, Star Schema build).
Build the models in Azure Analysis Services.
Consume in Power BI.
Does this seem like a good strategy? I am new to Azure Data Warehouse and our technical lead is on paternity, so we are unable to ask for his help.
I asked the external consultant what the impact would be directly applying all transformation workloads to Azure DW, and he has said that 'it's mpp, so processing is super-fast'.
Can anyone help? My team technical lead is on paternity so we can't get hold of him.
Azure is certainly a great platform for the modern data warehousing and analytics purpose, but ADW or not requires more study. Generally speaking, you can consider two options:
Volume is not huge ( < 10TB ):
SAP -> SSIS/ADF -> Azure SQL DB -> Azure Analysis Services (as semantic layer) tabular model with DAX -> Power BI
Volume is huge ( > 10TB ):
SAP -> SSIS/ADF -> Azure SQL DW -> Azure Analysis Services semantic layer -> Power BI
Of course, the volume is just one of many factors to consider when you decide the architecture, but it is an important factor from numerous real-world experiences where MPP may not be really necessary. The actual architecture and sizing require a lot more effort to research. The above points are the very general for your reference, to have something to start with and explore further.
If you look for more technical detail to bring SAP data to Azure, you can review our blog at here http://www.aecorsoft.com/blog/2018/2/18/extract-sap-data-to-azure-data-lake-for-scale-out-analytics-in-the-cloud and here http://www.aecorsoft.com/blog/2018/4/26/use-azure-data-factory-to-bring-sap-data-to-azure.
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.
Power BI doesn't allow users to share reports outside the organization. This is severely limiting and makes me wonder how I'm supposed to create a Power BI solution for my customers.
Why is this? And what is the preferred method for setting up my customers with Power BI?
Vote for this feature. Edit: this feature is now supported.
Alternatives would be publishing a public content pack like Salesforce does so it appears under the Get Data menu. Or sending your external people a Power BI Desktop file they can upload to their Power BI. Or you could provision users in your domain for your external people and have them log into your tenant.
Or if you want to host an Analysis Services model and let external people see it in Power BI here is an option.
Or if you prefer to use Azure Analysis Services then you can invite external users using B2B and they can consume in their own Power BI tenant. See the walkthrough here.