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

gopsvr 21 Reputation points
2021-02-11T17:02:37.083+00:00

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?

.NET
.NET
Microsoft Technologies based on the .NET software framework.
3,369 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.
12,702 questions
C++
C++
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,527 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. CathyJi-MSFT 21,086 Reputation points Microsoft Vendor
    2021-02-12T08:13:09.187+00:00

    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
  2. Olaf Helper 40,741 Reputation points
    2021-02-12T08:38:30.38+00:00
    0 comments
  3. gopsvr 21 Reputation points
    2021-02-16T17:18:09.313+00:00

    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