Post reply

SQL Server 2005 ODBC Driver

  • October 7, 2009 at 3:03 pm

    #135556

    We have a third-party software application that uses odbc to connect a SQL Server 2005 database to an application on a separate server. We've experienced some issues with odbc connection drops, and when the question of our driver selection was put to the third-party support group, they responded with the following:

    "The native client comes with SQL Server 2005 and allow to use also ADO and OLEDB. The standard driver is enough on system where you need to access to a DB that is not directly on the same server than your application.

    So we recommand to install only the standard driver (the native is perhaps too permissive) and, with our actual <development tool> 32bit version, the 32bit version too."

    In our OCBC Data Source Administrator window for User DSN ODBC Drivers, there are 2 SQL Server drivers listed:

    SQL Native Client (Version 2005.90.4035.00)

    SQL Server (Version 2005.85.1117.00)

    We are currently using the SQL Native Client. Is the second data source listed above what would be considered the "standard" version? Does anyone have an opinion about the SQL Native Client, and if it could have anything to do with our dropped database connections?

    Thanks for any advice!

    kay

  • October 8, 2009 at 7:10 am

    #1063419

    I have a correction to my post. The second odbc connection I listed as:

    SQL Server (Version 2005.85.1117.00)

    should be:

    SQL Server (Version 2000.85.1117.00)

  • October 9, 2009 at 7:51 am

    #1064066

    SQL Native Client is for SQL 2005

    SQL Server is for SQL 2000

  • October 9, 2009 at 7:54 am

    #1064069

    Thanks for the reply, William.

    Have you ever heard of a distinction between "SQL Server Native" and "SQL Server Standard" OCBC drivers? This seems to be the point of contention. We see the native driver, but we're at a loss as to where we would find (or if it exists) as a "standard" version.

  • November 3, 2009 at 9:45 am

    #1074363

    I'm reposting this question in the hopes of finding a solution (my previous post never received a response.)

    We are using a third-party software application on a SQL Server 2005 database for our core business. The application's support team has recommended we use the "SQL Server Standard" ODCB driver instead of the "SQL Server Native" driver.

    Has anyone heard of a distinction between these OCBC drivers? We see the native driver, but we're at a loss as to where we would find (or if it exists) a "standard" version.

  • November 3, 2009 at 10:47 am

    #1074412

    Have not heard of that distinction. I would guess that "standard" means the old "SQL Server" driver from SQL 2000. But that does not make much sense since the native client usually works better with 2005.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply