I have an odd question on connecting Power BI to a DB2 database.
I currently seem to have three similar drivers installed on my computer. If I look in ODBC data source administrator under the drivers tab I can see that they have the following names:
IBM DB2 ODBC DRIVER
IBM DB2 ODBC DRIVER - DB2COPY1
IBM DB2 ODBC DRIVER - IBMDBCL1
The first and third driver have the same version number (10.05.00.420). The second has a different version number (11.01.4041.600).
All three use the same DLL file (DB2CLIO.DLL).
All three seem to be able to connect Power BI to DB2 when used as a DSN, so I'm trying to establish which I should be using.
I want to know if these are different versions of the same driver which have been given different names during installation, or whether they are different drivers. And if they are different drivers, what is the difference?
Any advice would be appreciated please!
From IBM: "The IBM Data Server Driver for ODBC and CLI contains the copy name as part of the driver name. The default driver, IBM DB2 ODBC DRIVER, is set to the default IBM database client interface copy. The name of the driver for each installation is "IBM DB2 ODBC DRIVER - Copy Name"."
So if you select the first one, IBM DB2 ODBC DRIVER, ODBC will check with your settings and use the default driver copy on your computer, which will be one of the other 2 drivers. You set the default by using the db2swtch command.
The driver version should be tied to the version of DB2. Check with your DBA or just check with the right SQL for your DB2 platform (Windows, Linux, Z/OS, etc.).
Related
I am trying to connect Power BI to a third party database, i have created a system DSN and connected Power BI through the DSN to an ODBC driver. This works locally as long everything is on the same machine.
However, how can i configure the DSN so that it can be accessed by multiple users on many other different machines.
I have considered creating a DSN on the machine of each user but this seems redundant.
This question can be asked this way: is there a method that allows me to create one ODBC driver, one DSN, on the machine that holds the database and connect multiple users remotely to that ODBC driver using that one DSN ?
We have an older version (I think its 9) of informix running on our server that is the backend db for a vendor software. I have an ODBC for it to ms access but now they want to do powerbi stuff. Im finding the odbc is throwing error on certain tables and given that its vendor software, they're less inclined to upgrade the version. Everything I've seen seems to show that Informix doesn't like slaves that aren't informix and cloud isn't an option. Any suggestions for getting this data on a different db other than pulling csv files?
I am using SAS University edition and want to access the data from SQL server on my host machine(Windows 8.1 64 bit) in my SAS code. Virtual Machine(Oracle VM Virtualbox) OS is also Windows 8.1 64 bit. I am getting following error.
ERROR: The product with which the engine ODBC is associated is either not licensed for your system or the product license has
expired. Please contact your SAS installation representative.
SAS UE can only use Access to PC Files. You will not be able to connect to a database.
Either export/import your data manually via text files or try connecting an excel spreadsheet to your database.
SAS-datasets in a SAS/SHARE server can be made accessible for ODBC-compliant applications using the SAS ODBC Driver (http://support.sas.com/downloads/browse.htm?fil=&cat=40)
I want to access such a server through ODBC from SPSS - is this at all possible?
SPSS can use any standard ODBC driver.
Absolutely it can - have you used SPSS to connect to an ODBC data source before?
If not, you should be able to set up an ODBC connection using the ODBC Data Source Adminstrator (on Windows): https://learn.microsoft.com/en-us/sql/odbc/admin/odbc-data-source-administrator?view=sql-server-2017
And for SAS/SHARE in particular: http://support.sas.com/documentation/cdl/en/odbcdref/64777/HTML/default/viewer.htm#n1huqo74tuh90wn1vooxwjrqilgb.htm
I have an old ODBC application which is an ODBC 2.x application (using ODBC 2.x functions). It works fine when I connect to ODBC 3.x drivers. But now, I would like use some of the ODBC 3.x functions in my application, such as SQLBulkOperations.
My question is, whether I need make extra changes if I want to call ODBC 3.x functions in my ODBC 2.x application? If yes, can you give more details?
Note, all the drivers I use is ODBC 3.x
I believe you should be ok doing this as the driver manager looks after all this and will already be mapping your ODBC 2 API calls to ODBC 3 ones in the driver.
It is possible you may need to call SQLSetEnvAttr to set (SQL_ATTR_ODBC_VERSION) the version to 3 but I don't think so and you should hope not as it changes 1) ODBC 3.x codes for date, time, and timestamp 2) returns ODBC 3.x SQLSTATE codes.