Netezza odbc driver 64 bit download

Version If you are accessing this page from a non-English language version, and want to see the most up-to-date content, please select Read in English at the top of this page. You can download different languages from the US-English version site by selecting available languages. For details about this release on Windows, see the Windows release notes.

If you need to download the packages for offline installation, all versions are available via the below links. See also Installing the Linux driver. See also Installing the macOS driver. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Furthermore, there are two different folders in the Registry that get built.

The dll I installed, "nzodbcsetup. I am not exactly sure how to install this as a 32 bit driver on 64 bit windows, so that's why I changed the "Target Platform" in my. NET project from the default x86 to x There has to be a way to install it as a 32 bit driver as well because when I installed this on a 32 bit Windows XP box, the driver worked fine. What's weird is that Netezza's OLE drivers are separated.

They have a 32 bit and a 64 bit dll exe file for version 6. But the ODBC just has one, which is apparently both. Please comment is there a way in Windows to automatically install as 32 bit, not Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 9 years, 4 months ago. Active 9 years, 4 months ago. Viewed 6k times. Open ; System. ExecuteReader ; while rdr. OpenSubKey "Software" ; if reg! INI" ; if reg! MacGyver MacGyver What's the exact error message please?

ServerVersion' threw an exception of type 'System. InvalidOperationException' — MacGyver. Add a comment. Active Oldest Votes.

After doing this a second time, I noticed that the installer gives an option of a x86 and x64 version of the driver. On 64 bit Windows 7 or Server , the 32 bit version is clearly what the program actually uses when the application is set to x86 in Visual Studio project properties. That is obviously the driver in the SysWOW64 folder. Another very good explanation: community. Sign up or log in Sign up using Google. Sign up using Facebook.