ODBC Drivers 64-Bit

[NMahmoud]

I have 64 bit sqlserver 2008 installed on a 64bit Window Server,

and my problem is "there is no drivers listed in the 'ODBC/create New Data
Source' box other than the sql server",

1. I tried to install "64-Bit OLEDB Provider for ODBC (MSDASQL)" but the
installation give me the error "Not enough storage is available to process
this command"

2. I tried to install MDAC 2.8, but it did not run at all, it just flashed
and died

3. Installed "CompChecker", and I perform analysis to determine the release
version, I get unknown version

4. the register

"HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer" =
6.0.6001.18000

"HKEY_LOCAL_MACHINE\Software\ODBC\ODBCINST.INI" has only the sqlserver's

[Sylvain Lafontaine]

First, many ODBC providers such as those for Access or Excel are 32 bit
driver and cannot be accessed from a program running under the 64 mode of
Window Server 64 bit and installing the 64 Bit OLEDB Provider for ODBC
(MSDASQL) will change nothing to that.

Second, your installation problems look strange. What kind of 64 bit Window
Server do you have? Is this Itanium or the more regular Intel X64 flavor?

[NMahmoud]

thank you for your response Sylvain, you are right, we installed the 64 bit
Oracle client utilities and we were able to see Oracle odbc driver listed.
We have X64,

and I thought that 32/64 translation layer will make the 32
applications/drivers appear to the system as 64, apperantly not.
but I was able to see the 32 ODBC dirvers when I run the 32bit
"odbcad32.exe" which I found in

C:\Windows\winsxs\x86_microsoft-windows-m..-odbc-administrator_31bf3856ad364e35_6.0.6001.18000_none_444fe75e3db70c2d

[Sylvain Lafontaine]

Exactly: there is no translation layer available at this moment; so if you
don't have a 64 driver available, you cannot use a 32 bit driver instead
from the 64 world. The 32 bit drivers that you can see with the 32 bit
version of odbcad32.exe are only for the programs running under the 32 bit
emulated mode (WOW64) and cannot be accessed from any program running under
the native 64 bit mode.

[Ivan Sanders]

Irrespective of whether your Microsoft SQL Server instance is 64-bit, the Visual Studio IDE is a 32-bit application and as a result all OLE DB and .Net Providers must be 32-bit, along with any subsequently interfaced components such as ODBC drivers. (This is whay you cant choose any 64=bit DSNs as datasources & if you create a 32-bit DSNs you will error with an architecture mismatch)

This means that when you are developing and debugging SSIS, SSAS, & SSRS applications you will require a 32-bit Provider and where necessary the 32-bit ODBC drivers.

When run your final SSIS, SSAS package, if it is deployed against a Microsoft SQL Server instance which is 64-bit, it will require a 64-bit Provider and where necesaary a 64-bit ODBC driver.

Therefore, with 64-bit instances of Microsoft SQL Server you will require both 32-bit and 64-bit components to allow ease of use in taking advantage of the available features

It was worse with Visual Studio 2005 on a 32-bit OS, the 64-bit compilers were not installed by default, you will need to go to custom setup and check the option.

Bottom Line, you can create ODBC DSNs that are 32-bit and then compile your code and have the equivalent DSNs (Same, etc) on your production x64 environment... Its beyond my ability to understand why VS2005 through VS2010 allow you to compile x64 code, but limit your ability to use x64 drivers where necessary.... There are always methods to work around an issue....