Creating a linked server in SQL Server 2014 SSMS to remote DB2 - tsql

I am running 64 bit SQL Server 2014 Express and have a 32 bit DB2 Express-C on the same machine.
In the 64 BIT SQL Server can I create an ODBC connection to a remote DB2 system without having to install a local 64 bit version of DB2.
If I could go back and redo everything I would install the 32 BIT SQL Server but it is now to involved and performing an uninstall and reinstall would be to risky.
It should also be noted that I have successfully used the 32 BIT IBM ODBC driver to do a remote connect via 32 BIT version of WINSQL but when I run the 64 BIT version of WINSQL I can not make a connection to the remote DB2 system because no 64 BIT version of the driver is found.

I think the answer is here: http://www-01.ibm.com/support/docview.wss?uid=swg21384435
How to install 32-bit ODBC driver on 64-bit system.

Related

oracle 32 bit client on a windows 7 64 bit computer

Trying to install Oracle 9i (32bit) client on a Windows 7 64bit computer. Seems to install fine, but when trying to run anything, such as the Net Configuration Assistant, it doesn't do anything, no errors, and nothing started in the background.
So the question is:
Can the 32 bit client of Oracle be installed on a 64 bit Windows 7 PC? Or does it need to be a 64 bit client?
You can install a 32 bit client, and if your software is 32 bit, you need to install the 32 bit client to use it, even on a 64 bit system.

does oracle10g client( version 10.2.0.0) compatible with windows server 2008 standard 32 bit service pack 2

I am trying to install oracle 10g client version 10.2.0.0 on windows server 2008 standard 32 bit machine with service pack 2. The oracle 10g client is getting installed but when i try to connect to oracle 9i server on another machine it is giving error "test does not succeeded". I have tested same using windows 7. On that it is working fine and getting connected to oracle 9i server. But i want this to be done on windows server 2008 standard only. Please suggest what i can do in this case?

32bit and 64bit Versions of PostgreSQL 9.1 ODBC are Mixed Up

I've installed both the 32bit and 64bit versions of psqlODBC 9.1. When I configure both a 32bit and a 64bit System DSN they get written to the ODBC.ini file incorrectly:
[ODBC 32 bit Data Sources]
pg_crdb_latest=PostgreSQL Unicode (32 bit)
pg_crdb_latest_32=PostgreSQL Unicode(x64) (32 bit)
[pg_crdb_latest]
Driver32=C:\Program Files (x86)\psqlODBC\0901\bin\psqlodbc35w.dll
[pg_crdb_latest_32]
Driver32=C:\Program Files\psqlODBC\0901\bin\psqlodbc35w.dll
The pg_crdb_latest DSN was added using the 64bit ODBC Data Source Administrator. The pg_crdb_latest_32 DSN was added with the 32bit one.
FYI - I installed the 32bit version first, then the 64bit version.
The outcome is I get this error when trying to connect to PostgreSQL 9.1 64bit in SAS 9.2 64bit:
ERROR: CLI error trying to establish connection: [Microsoft][ODBC
Driver Manager] The specified DSN contains an architecture mismatch
between the Driver and Application
Any ideas how to set this right? I'm running Windows 7 Pro 64bit.
This link explains it all
http://www.easysoft.com/developer/interfaces/odbc/64-bit.html#odbc-windows
So two things:
Windows has very poor file and directory naming conventions regarding ODBC - hence the confusion
64bit PostgreSQL ODBC is currently very slow (10x slower than SAS to SQL 64bit via OLEDB) - I'll investigate this further

ODBC Oracle driver in Windows Home Basic Premium

I am using the operating system Windows Home Basic Premium. I installed Oracle 10g Express Edition also 11g, it installed correctly but when I would go for adding driver from ODBC I didn't find any Express driver.
That's why I can't run any Java database project; it shows me driver not loaded. This is first I face problem using any software.
First off, in general, you should not be using ODBC if you are developing a Java application. Java applications generally use the JDBC driver to connect to the database. It is possible to use a JDBC to ODBC bridge driver but that was really only appropriate years ago when not every database had a JDBC driver. There would be no reason to use a JDBC to ODBC bridge driver to connect to an Oracle database in an application built today.
That being said, are you using a 32-bit version of Windows or a 64-bit version of Windows? Did you install 32-bit versions of Oracle or 64-bit versions of Oracle? If you are using a 64-bit version of Windows, the default ODBC Driver Administrator will only display the 64-bit ODBC drivers that are installed. If you installed 32-bit versions of Oracle, you'll need to open the 32-bit ODBC Driver Administrator at C:\Windows\SysWOW64\odbcad32.exe in order to access the 32-bit ODBC drivers.

allround automations pl/sql developer on windows 7 - TNS over IP connect to remote db

I am really having very hard time making PL/SQL developer PL/SQL Developer work on my windows 7 64-bit OS. I have Oracle 10g standard edition installed already. I tried with PL/SQL developer version 7 and 8 with no luck. Do anyone tried doing it?. Main objective is to just establish a TCP over IP connection to a remote Oracle 10g database from PL/SQL developer. The PL/SQL developer website states it supports windows 7 though but it's making me crazy.
I finally got PL/SQL Developer working on my Windows 7 OS. Here goes the step by step instructions on how I did it.
First installed Oracle 10g 32-bit client runtime environment which is sufficient enough for opening a TCP over IP connection to a remote Oracle 10g database from PL/SQL Developer. It is also possible to connect using Oracle InstantClient (which is more light only 300 Kb) InstantClient_PL/SQL.
Than installed PL/SQL Developer version 8.0.4 (latest as of now) and copied over tnsnames.ora file into C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN.
Now I can open a vpn connection for a remote database and connect directly to the remote db from PL/SQL developer using a TNS over IP connection.
The only caveat here is to open PL/SQL Developer as an administrator. This is where I went wrong and PL/SQL developer crapped out with a blank window.