I need to connect Power BI to SAS using an OLE DB connection (can't use ODBC nor the native connection). Here is the string from the build:
provider=sas.IOMProvider.9.45;data source="iom-name://SASApp - Logical Workspace Server";mode="ReadWrite|Share Deny None";sas cell cache size=10000;sas port=0;sas protocol=0;sas server type=1;sas metadata user id=dxru984;sas metadata password=XXXXX;sas metadata location=iom-bridge://lhwappb1.xxx-xx.xxx:8561
I also tried with this one:
Provider=sas.IOMProvider.9.45;Data Source=iom-name://SASApp - Logical Workspace Server;SAS Cell Cache Size=10000;SAS Port=0;SAS Protocol=0;SAS Server Type=1;SAS Metadata User ID=dxru984;SAS Metadata Password=xxxxxxx;SAS Metadata Location=iom-bridge://lhwappb1.xxx-xx.xxx:8561
The first string works perfectly with Excel but not in PowerBI with that error message:
OLE DB : Format of the initialization string does not conform to the
OLE DB specification
Any idea?
I managed to connect to SAS Federation Server data using the following connection string:
provider=sas.IOMProvider.9.45;data source=blablabla2.abc.pt;sas port=1234;sas protocol=2;sas metadata user id=******;sas metadata password=**********;sas metadata location=blablabla1.abc.pt:5678
Hope this helps,
Rita Dias
Related
Good morning,
I am working with PowerBI premium and I am looking to connect a datasets existing in a premium workspace.
I need to connect to SQL Server Analysis services using the following connection string:
powerbi://api.powerbi.com/v1.0/myorg/workspacename;initial catalog=report_name
It works when connecting from PowerBI desktop but I am unable to connect to the datasets when I publish my report in the same workspace as the datasets.
The purpose of using SQL Server Analysis service instead of "Connect to PowerBI Datasets" is that I can work locally.
2 files:
1 datasets (Model)
1 report connected through "localhost:PortNumber"
When ready I can publish my datasets, then change datasets connection string in my report file and finally I can publish the report online for consumption.
Would someone know how I can do that without having an error after publishing the report online?
I have designed a power bi report for a client using data set as his SQL Server database backup in my local system, and publish it on his provided power bi service account, now how do i connect this publish report with my client's local SQL server database?
In other words how my client be able to connect his local system's SQL database with this report?
You can use parameterized connection where you can store your local database access and client database access details, by using:
I have a MSSQL server on-prem and followed the steps from Microsofts Docs
in order to install the gateway.
Than i managed the gateway via manage gateways within power bi (cloud) and the test there worked and i got the green check.
Now the question how do i get the data from the gateway into a dataset? when i try to add a new dataset there and click on data bases i only get Azure SQL Database, Azure SQL Data Warehouse, SQL Server Analysis and Spark on Azure HDInsight but now sign of my fresh data gateway to my on-prem db.
Currently you can only access on premise SQL Server databases by building a model & publishing it to powerbi.com using the Power BI Desktop.
If you select "Import" as your connection option, Power BI will store the required data online. You will be able to query on that fixed data and work with it even when your connection to the on premises server is down. You can update your fixed dataset with new data if your connection is properly defined in your gateway.
If you select "DirectQuery" in your Power BI Desktop you will require an active connection to the On premises server for any reporting to work online. On the up side, it'll work on live data and will not store any data online.
When publishing, Power BI Desktop will try to match your connections used in your report to the ones defined in your gateways. If it can find a match, it'll automaticly link those up. It'll give you an informational message to let you know if this step succeeded after publishing. At the same time it'll add a dataset using the same data you used in the reports you just built.
We are working on the ETL. How to read data from the POSTGRESQL data base using streams in DATA ANALYTICS SERVER and manipulate some operations using the streams and insert the manipulated data into another POSTGRESQL data base on a scheduled time. Please share the procedures to follow.
Actually, you don't need to publish data from your PostgreSQL server. Using WSO2 Data Analytics Server (DAS) you can pull data from your database and do the analysis. Finally, you can push results back to the PostgreSQL server. In DAS, we have a special connector called "CarbonJDBC" and using that connector you can easily do this.
The current version of the "CarbonJDBC" connector supports following database management systems.
MySQL
H2
MS SQL
DB2
PostgreSQL
Oracle
You can use following query to pull data from your PostgreSQL database and populate a spark table. Once spark table is populated with data, you can start you data analysis tasks.
create temporary table <temp_table> using CarbonJDBC options (dataSource "<datasource name>", tableName "<table name>");
select * from <temp_table>;
insert into / overwrite table <temp_table> <some select statement>;
For more information regarding "CarbonJDBC" connector please refer following blog post [1].
[1]. https://pythagoreanscript.wordpress.com/2015/08/11/using-the-carbon-spark-jdbc-connector-for-wso2-das-part-1/
I'm trying to use an OLEDB connection to connect to my SAS datasets from QlikView.
I am able to set up the connection, but I am not able to load my data. Executing the data import results in the following error: "the local provider does not currently support sql processing"
My loading code looks like this:
LOAD "account",
balance,
"open_closed";
SQL SELECT *
FROM "BASE_DATA";
Is there any way to solve this?
We read SAS data into QlikView using SAS ODBC driver that connects to SAS/SHARE.
This requires that you have one of the following three:
1. SAS/SPD Server
2. SAS/SHARE Server
3. SAS locally on desktop (will not work on server license)