How does ADO.Net know which version of the SQL Native Client to use if you have both SQL 2005 and 2008 in your environment?

How does ADO.Net know which version of the SQL Native Client to use if you have both SQL 2005 and 2008 in your environment?

  • Modify SQL trigger to work when inserted table contains more than one row
  • Properly closing a database connection - VBScript + MS SQL
  • Microsoft SQL Server insert from select query
  • INT vs Unique-Identifier for ID field in database
  • Inserting a multiple records in a table with while loop
  • Can I use a SQL Server CTE to merge intersecting dates?
  • Ignore Two Columns in Update Trigger
  • How to set collation for a connection in SQL Server?
  • expression of non-boolean type
  • Adding multiple parameterized variables to a database in c#
  • “Can't find PInvoke DLL 'dbnetlib.dll'.” error in Smart Device Application
  • Classic ADO and Table-Valued Parameters in Stored Procedure
  • One Solution collect form web for “How does ADO.Net know which version of the SQL Native Client to use if you have both SQL 2005 and 2008 in your environment?”

    For basic services, they’re backward compatible so you don’t even have to worry about it: if 2008 native client is installed, it should connect to 2005 or 2008 databases transparently.

    The only problem you run into is some parts such as DTS or SQL-DMO, which apparently require a separate download for backwards compatibility:

    http://www.microsoft.com/downloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en

    Installing those will mean that you won’t have to worry about the existence of the 2005 native client on the system.

    Does that help?

    MS SQL Server is a Microsoft SQL Database product, include sql server standard, sql server management studio, sql server express and so on.