Upgrading to 'ODBC Driver 17 for SQL Server' from 'SQL Server Native Client 11' for ADO.

gopsvr 21 Reputation points

1)Im using ADO(msado15.tlb) in C++ to connect to Local/Remote SQL Server. Now changing ODBC driver from 'SQL Server Native Client 11' to 'ODBC Driver 17 for SQL Server'. Is there any thing to be taken care (Multisubnet,XML datatypes,TLS,AD User)? Should i specify "Provider=MSOLEDBSQL;" in the connection string to get any advantage?

2)Any advantage over ADO(_ConnectionPtr) for MFC CDataBase when using only ODBC-DSN?

Microsoft Technologies based on the .NET software framework.
2,288 questions
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
11,558 questions
A high-level, general-purpose programming language, created as an extension of the C programming language, that has object-oriented, generic, and functional features in addition to facilities for low-level memory manipulation.
3,307 questions
{count} votes

3 answers

Sort by: Most helpful
  1. CathyJi-MSFT 21,056 Reputation points Microsoft Vendor

    Hi @gopsvr ,

    I can only reply the question about SQL server.

    > Should i specify "Provider=MSOLEDBSQL;" in the connection string to get any advantage?

    Provider=MSOLEDBSQL means using Microsoft OLE DB Driver for SQL Server connection strings.

    Driver={ODBC Driver 17 for SQL Server} means using Microsoft ODBC Driver 17 for SQL Server connection strings.

    If the response is helpful, please click "Accept Answer" and upvote it, thank you.

    0 comments No comments

  2. Olaf Helper 36,001 Reputation points
    0 comments No comments

  3. gopsvr 21 Reputation points

    Thank you But i was looking for what to use. Found ODBC 17 has some issues with xml,varchar(max) fields where the MSOLEDBSQL returns the values properly. CDatabase is also giving issues for xml columns. With Convert to varchar can solve this issues.

    0 comments No comments