Active2 years, 5 months ago
I am trying to create a linked table in a 64-bit SQL Server to Informix, and the SQL server does not list Informix ODBC in the DSN list. I have downloaded the 64-bit Informix Client SDK, however, despite the fact that it states 64-bit Informix Client SDK, it only appears in the 32-bit ODBC DSN. I tried to create a linked table in a 32-bit SQL Server and I was then able to see Informix ODBC DDN.
Informix Client Sdk Download
If you downloaded the Informix SDK install from CiscoUnityTools.com that's a 32 bit driver only - all tools written for Connection are built for 32 bit and require the 32 bit driver regardless of if the platform is 32 or 64 bit.
I was just wondering that if there is an Informix Client SDK that would show in the 64-ODBC DSN, not the 32-bit?
- 64-bit MSDASQL for Windows 2003 is now available for. To access data sources through an ODBC driver. MSDASQL is an OLEDB provider that connects to.
- Informix ODBC Driver Install is a driver that makes possible that any tool connect to the Connection 2.1(1) or later database.
- Our Single-Tier ODBC Drivers for Informix are a single component installed on a data-consuming machine - depending on the architecture in which the driver is.
- Hi, please, does anyone know where i can Download Informix Client ODBC driver 64 bit????? I have downloaded IBM Informix Client SDK Install 3.50 TC9 for all 32 and 64 bit Windows Systems but when i.
Also is there a way of linking a 64-bit SQL Server to Informix please?Thanks.
TallTedInformix 64 Bit Odbc Driver Download
7,25822 gold badges1515 silver badges2929 bronze badges
user3787561user3787561
4 Answers
Create a DB Link in SQL Server to Informix
I used the following Software environment:
- SQL Server 2012
- Informix SDK 4.10 FC2
- Informix 11.5
First Set some Properties for Ifxoledbc Driver:
Then Create Linked Server:
General Settings - Datasource is your DB and your Server Name
Security Settings - Add valid Informix Database Credentials
Server Options - Set RPC and RPC Out to True
I use the db link for calling a stored Procedure in Informix and writing the data to SQL Server.
SGeisSGeis
Did you use the 64 bit version of ODBCAD32.EXE to create the DSN?
There are two versions of the ODBC administrator.
This one is the 32 bit version:
It can only see 32 bit drivers, and only 32 bit processes can see it's DSN's
This one is the 64 bit version:
It can only see 64 bit drivers, and only 64 bit processes (i.e. SQL Server 64 bit) can see it's DSN's
Even better you could define a DNS-less connection which doesn't use a DSN, it uses the driver directly. Then you can avoid this confusing step altogether.
Nick.McDermaidNick.McDermaid12.6k33 gold badges2828 silver badges5858 bronze badges
I would have used the Comment feature, but I do not have enough 'Reputation Points' to do so.
The answer of SGeis, above, is on the money. It was hard for me to find such a clear, straightforward answer. Snapshots of the dialog boxes help immensely.
Let me add to his answer the following:
- The Data Source fill-in (YourDatabaseName@YourInformixServerName) could be something as simple as Fred@Barney, rather than what I tried, namely, [email protected] or [email protected]:32002 (the latter specifies a port/service number).
- Once you create the linked server, if you go back into its General properties page, you will see that you cannot edit what you typed for Linked Server, Product Name (Why isn't this called 'Provider Name,' since Ifxoledbc is listed under Linked Servers/Providers in the Object Explorer tree?), Data Source, etc. So, if your connection fails because you mistyped something, it is unclear how to fix it.
![Informix Odbc Driver 64 Bit Download Informix Odbc Driver 64 Bit Download](/uploads/1/2/6/3/126300761/958618689.jpg)
Here is what you may do:
- Right-click the linked server.
- Beneath 'Test Connection,' look for 'Script Linked Server as.'
- Click the latter, and, then, each of the following: 'DROP And CREATE To'and 'New Query Editor Window.'
- In the script text that appears, type replacement info for those settings that were grayed-out and uneditable.
- Press F5 to run the script and thereby apply your changes. In doing so, the existing linked server is dropped, and a new one is created.
- Open up your linked server's Security properties page and re-enter any connection password (even though asterisks -- suggesting that the password is filled and correct -- may appear in the corresponding entry). Also, examine the General properties page. Make sure that your changes stuck. Even though you ran the script and received no error, SQL Server will blank out fill-ins such as 'Linked Server,' 'Product Name,' and 'Data Source' if, for example, you, as I did, had a brain aneurism and chose the wrong drop-down item for 'Provider.'
- As noted above, click 'Test Connection,' to verify that your changes work.
JOINtheFunJOINtheFun
I was able to set up a linked server without Ifxoledbc. Once my System DSN for the 64-bit ODBC driver was set up (and tested OK), I set up a linked server using the Microsoft OLE DB Provider for ODBC Drivers.
Linked Server: UCCX
Provider: Microsoft OLE DB Provider for ODBC Drivers
Product name: IBM Informix ODBC Driver (probably could be anything but I named it the same as the ODBC Driver and it worked).
Data Source: UCCX (the name of your System DSN).
Provider: Microsoft OLE DB Provider for ODBC Drivers
Product name: IBM Informix ODBC Driver (probably could be anything but I named it the same as the ODBC Driver and it worked).
Data Source: UCCX (the name of your System DSN).
On the security tab I mapped a local login to the same remote user/password as the one set up in the System DSN itself.
![64-bit 64-bit](/uploads/1/2/6/3/126300761/607878156.png)
And another way to consume the System DSN is via OPENROWSET. This works even without setting up a linked server:
FloookFloook