Helooo everyone
I'd like to design an oracle (apex) database that is linked to ArcMap, or vice versa, so that the data is synchronized
I tried to link to oracle through ArcMap, but I did not get any results, as shown in the picture.
Thanks to all
Database connection
The message complaints about the Oracle client. In the machine that you are running ArcMap, you need an Oracle client to connect to your database. The client should allow you to connect to your DB directly through SQLplus.
Related
Live connections
When connecting to SQL Server Analysis Services,
there's an option to either import data from or connect live to, the
selected data model. If you use import, you define a query against
that external SQL Server Analysis Services source, and the data is
imported as normal. If you use connect live, there's no query defined,
and the entire external model is shown in the field list.
My understanding was that import/direct query can be used to query a data source like SQL server. Where as live mode is used to connect to an existing power bi dataset, or SSAS, or azure analysis service.
The above quote says When connecting to SQL Server Analysis Services, there's an option to either import data from or connect live to, the selected data model. - So does this mean that the live mode allows us to choose between import/direct query to the live model?
When connecting to SQL Server Analysis Services, there's an option to
either import data from or connect live to, the selected data model.
This quote means that you do not have to use a live connection with SSAS models. Instead you can construct a query and import the data. The dataset would be limited to whatever was in the query. If you use a live connection, you have access to the entire model.
I have an accessDB which using ODBC connection to SQL and used in queries.
Tried to use the queries to create a report on PowerBi, Issue is whenever I tried to update the dataset it gives me ODBC--call failed.
Tried created the ODBC connection on gateway machine. they are all 32 bit [ODBC/Power Bi Desktop] etc.
Can someone please help?
had to install office 64bit and access 64bit driver
also had to refresh all the linked tables and views from access to rectify the issue.
I have created a new Azure SQL Data Warehouse database on a new logical server from the backup of a Azure SQL Data Warehouse database on a different logical server (using the Azure portal). I created the LOGINs on the new MASTER database for the users that would connect to the new Azure SQL Data Warehouse database. The users were restored to the new Azure SQL Data Warehouse database as expected per:
SYS.DATABASE_PRINCIPALS
Now when I attempt to connect with those users, I receive an error:
Sqlcmd: Error: Microsoft ODBC Driver 11 for SQL Server : The instance of SQL Server you attempted to connect to does not support CTAIP..
We use sql-server authentication, running the following on both the original and new MASTER:
CREATE LOGIN
the_userID
with password = 'xxxxxxxxxxxxxxxxx'
;
GO
and the following pattern on the original ADW database:
CREATE USER [the_userID] FROM LOGIN [the_userID]
;
GO
Is there any solution other than dropping and reCREATEing the users in the new ADW database?
CTAIP error is a rather poorly worded error message indicating the login (in master) does not have a corresponding user in the DW.
In this case, you need to drop the existing user in the DW and re-create it for the login in master.
It doesn’t work automagically (yet) because we track the association using security identifiers (SID) not names and the new login in master has a new/unique SID. AAD logins and contained users (not currently supported in DW) don’t have this problem.
I am planning to automate the KILL of user queries running over a configurable amount of time. I see that
sys.dm_pdw_exec_sessions
has the login_name, but the client_id column looks to me like an Azure IP (104.*) and not the IP (10.*) from my company's servers/PCs.
Is it possible to know the client context for an ADW query?
If you connect from your laptop to Azure SQL DW the IP will usually match your public IP. Compare to http://www.myipaddress.com and see if it matches. It won't be your internal 10.* IP address because you can't put Azure SQL DW on a VNET at the moment.
sys.dm_pdw_exec_sessions also has app_name, which gives some good details, for example:
'Mashup Engine' in the above example is Power BI Desktop.
You could also instigate a policy that all queries had to use the LABEL syntax to give additional query context, kill queries that don't comply? See below for additional details:
https://learn.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-develop-label
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.