Link to home
Start Free TrialLog in
Avatar of Daniel Flores Olmos
Daniel Flores OlmosFlag for Mexico

asked on

MSSQL Driver missing in Windows Server 2008

Hi,

One aplication I use, needs to configure an ODBC conection from firebird to SQL. I have it working before in my Windows 2003/ with the MSSQL Database Driver Name and it was working correctly but actually, I have migrated all the apps to my Windows 2008 Server and that particularly app is not working because I can't find the MSSQL Driver to establish the ODBC connection, I can only find SQL Server and SQL Server Native but the connection doesn't works. Does anybody know how to install that MSSQL Database Driver Name in Windows Server 2008 Standard?

Thanks!
Avatar of Dave Baldwin
Dave Baldwin
Flag of United States of America image

The SQL Native Client is required to support ODBC.  In my driver list for ODBC, I have SQL Native Client 9 for SQL Server 2005 and 10 for SQL Server 2008.  There are also versions 11 for SQL Server 2008 R2 and 12 for SQL Server 2012.  They are all available for download from Microsoft on the Microsoft® SQL Server® xxxx Feature Pack pages.  They are all called 'sqlncli.msi'.  The one for SQL Server 2012 is available here: http://www.microsoft.com/en-us/download/details.aspx?id=29065  It supports connections to Microsoft SQL Server 2005, 2008, 2008 R2, and SQL Server 2012.
Avatar of Daniel Flores Olmos

ASKER

I'm sorry, I forgot to say that in my old server I had Windows 2003 Server with SQL Server 2000 and in the new server I have Windows 2008 Server with SQL Server 2008
Last server is 32bits, new server is 64bits
Then you should get SQL Native Client 11 or 12.  I don't know what changes you need to make in your connection string from Firebird.
well, in facts I don't create a ODBC creation as well, my app creates it through the configuration wizard, but it needs the MSSQL driver to work fine.
Then I think you need to update your app since that driver won't work on SQL Server 2008.
ASKER CERTIFIED SOLUTION
Avatar of Rich Weissler
Rich Weissler

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi,

If this DSN is being created by the app, while the newer drivers will work better I suspect the easiest thing is to look for the latest MDAC from Microsoft. I think the latest is version 2.8.

Run that up.

I'm pretty sure it wont affect the other drivers you have the SQL Native Driver.

I suggest you try this on a test system first.

Regards
  David
I'm trying!
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial