Devart Forums

Hi,

when is it necessary to install SQL Server Native Client (sqlncli.msi)?

Does the SDAC component support a direct mode without the native client?

Is there a difference with the connection to SQL Server (Express) and LocalDB?

I'm currently working on an installer for our application and for easy deployment we'd like to distribute LocalDB with our application, but we found that on a clean Windows install it's not enough to install LocalDB (SQLLocalDB.msi), but we also have to install the Native Client MSI.

How does SDAC communicate with LocalDB, as far as I can see this works using a named pipe?

We are using version 6.6.12.

Hello,

SDAC can work with SQL Server using two providers: OLE DB that is shipped with MDAC, and SQL Native Client that is shipped with SQL Server. To choose the needed provider, you can use the TMSConnection.Options.Provider property. In case of using OLE DB, you do not need to install anything on the client machine because MDAC is supplied with Windows. In case of using SQL Native Client, you need to install SQL Native Client on the client machine.

Note, that it is possible to connect to LocalDB only using SQL Native Client 11 (is shipped with SQL Server 2012). That is not our limitation. You can find the information about LocalDB at http://technet.microsoft.com/en-us/libr ... 10202.aspx . For more information, please contact the Microsoft support.

Ok, so I have to install SQL Native Client to access LocalDB.

As for the "normal" SQL Server: Is there any advantage of using SQL Native Client as the provider over the OLE DB provider?

Yes, there are advantages of using SQL Native Client instead of OLEDB. Only using SQL Native Client, it is possible to use some features of SQL Server, such as notifications, Table-Valued Parameters, FILESTREAM, sequences, etc.