We are trying to connect our ssas cube to big query database on Google cloud.Which connectivity provider do we need to use?
I came across one of the web link where there are saying there is cdata provider we can use for this but What I need to check here, is there any other efficient way
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.
There is an option to connect a Cloud mySQL instance from BigQuery. I just wanted to know how we can connect a Cloud SQL Server instance to BigQuery.
SQL Server:
There are a bunch of third-party extensions/tools that provide this service. One of them is SSIS Data Flow Source & Destination for Google BigQuery, which is Visual Studio extension that connects SQL Server with Google BigQuery data through SSIS Workflows.:
https://www.cdata.com/drivers/bigquery/ssis/
https://marketplace.visualstudio.com/items?itemName=CDATASOFTWARE.SSISDataFlowSourceDestinationforGoogleBigQuery
In regards to using SQL Server Integration Services to load the data from the on-premises SQL Server to BigQuery, you can take a look for this site. You can also perform ETL from a relational database into BigQuery using Cloud Dataflow, the official documentation details how it can be done, you might need to use Cloud Storage as an intermediate data sink.
Cloud SQL:
BigQuery allows to query data from Cloud SQL by using federated query. The connection must be created within the same project where your Cloud SQL instance is located. If you want to query your data stored in your Cloud SQL instance from BigQuery located in another project, please follow the steps listed below:
Enable the BigQuery API and the BigQuery connection API within your project.
Create a connection to your Cloud SQL instance within the project by following this documentation.
Once you have created the connection, please locate and select it within BigQuery.
Click on the SHARE CONNECTION button and grant permissions to the users that will be use that connection. Please note that the BigQuery Connection User role is the only needed to use a shared connection.
Additionally, please notice that the "Cloud SQL federated queries" feature is in a Beta stage and might change or have limited support (is no available for certain regions, in which case, it is required to use one the supported options mentioned here). Please remember, that to use Cloud SQL Federated queries in BigQuery, the intances need to have a public IP.
If you are limited e.g. by region, one good option might be exporting the data from CloudSQL to Storage as a CSV, and then load it into BigQuery. If you need, it is possible to automate this process using Cloud Composer, refer to this article.
Other approach is to extract information from Cloud SQL (with exports) and import it into BigQuery through load jobs, or streaming inserts.
I hope you find the above pieces of information useful.
It is possible, but be warned the feature is currently Beta
https://cloud.google.com/bigquery/docs/cloud-sql-federated-queries
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.
I have Tableau Server connecting to a Drill view. I want to deal with authorisation in Drill so I need Drill to know who is requesting the data from Tableau Server. For this I need impersonation to work as otherwise session_user in Drill will always be Tableau Server service account and not an actual person connecting to Tableau Server.
This link seems to suggest that impersonation in Tableau works only for SQL Server:
https://onlinehelp.tableau.com/v10.1/server/en-us/impers_requ.htm
It would be strange considering how many datasources Tableau supports... Is it really not possible? And if it is not, are there any workarounds?
My versions are: Tableau 10.1 and Drill 1.10
I think the confusion here because of Tableau doesn't mention about Drill anywhere in documentation. You can treat Drill as a SQL server and use impersonation with it. Drill supports something called inbound impersonation which allows a connection user (session_user) in drill to impersonate a Tableau end user. The corresponding parameter for connection string of Drill is delegation_uid.
I was trying my hands on building Cubes using AdventureWorksOlap database. I successfully build what I was trying to do. Now my concern is that I want to deploy the cube to a server so that rest of the team members can use this cube as a datasource while generating their SSRS reports (might be some other tools).
I have heard that SSAS does not allows Sql Authentication. So,
1) how will the members access the cube?
2) What authentication changes do I need to incorporate?
3) How can the other developer using his computer's SSMS access the cube and make changes to it (just like we can do it in the OLTP database)?
4) I need to prepare a dashboard using this cube. Any suggestions on this one.
Thanks in advance.
1) Windows Authentication
2) none.
3) Once the cube is deployed you cant change it. Actually you can change some things like partitions and roles, but you cant add a dimension for example. You need to change the project on BIDS and redeploy it
I would recommend starting with Excel Pivot Tables to learn what type of dashboard you will want to create. By working with the end-users, you can understand what information they want/need to see.
Regarding security, as mentioned, by design cubes use Windows auth only. Here's a blog that talks about circumventing standard security.
Also, I have posted a series of videos on how to create OLAP cubes SSAS in SQL Server 2008 using BIDS. You may find this series helpful.