odbc drivers version


  I have a 64 bit server (windows 2008R2) with a 32 bit app on it that connects to a 32 bit MS SQL 2005 database. Does the odbc driver bit version (32 or 64) have to comply with the application bit version or the database bit version?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hypercat (Deb)Commented:
It has to comply with the workstation OS version.  For Windows 7 workstations, you want to use the SQL Native Client 10 version.  If it's a 64-bit workstation, you need to use the odbcad32.exe file from the SYSWOW64 folder to set up the ODBC connection; if it's a 32-bit workstation, you use the standard ODBC setup from Control Panel/Administrative tools.

As far as I'm aware, neither the SQL version (for SQL 2005 and above anyway) nor the application version will have any bearing on the ODBC setup process.
Steve WalesSenior Database AdministratorCommented:
The above is partially true.

The bitness of the application drives what ODBC driver to use.

If you install 64 bit ODBC drivers on a 64 bit OS and try to use a 32 bit application, it won't find the driver.

I find this all the time in my Oracle environments as we've been rolling out 64 bit Windows 8.1 to users.  We have installed both the 32 bit and 64 bit Oracle clients on the machines because MS Office is 64 bit but some of the other tools in use are 32 bit.

Bitness of the App drives the driver used.

How to access the appropriate ODBC administrator as described by hypercat is correct though.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LuckyLucksAuthor Commented:
For selecting the driver for the data source, I have two options:

1. SQL server (SQLSRV32.dll)
2. SQL Native Client 10.0 (SQLNCLI10.dll)

Why should I choose the SQL native CLient 10 over the SQL server?
Steve WalesSenior Database AdministratorCommented:
I don't claim to be extremely knowledgeable in the details of this area, but I did find a blog entry from the SQLNCli team on Microsoft's site that seems to address this at least in part.

It would appear that SQLSRV32.dll is a much older version and that SQLNCLI10.dll is the more recent.

The blog entry, for reference, is here: http://blogs.msdn.com/b/sqlnativeclient/archive/2008/02/27/microsoft-sql-server-native-client-and-microsoft-sql-server-2008-native-client.aspx
Vitor MontalvãoMSSQL Senior EngineerCommented:
A Native Client should be used whenever it's possible since should have more and recent methods than other drivers. And being a native client should also be better for the performance.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.