Endpoint Protection

Hi ALl

good morning.

 

As we have upgarded our Sep to 14 MP 2 and we have SQL 2008 r2 databse installed on remote computer . now we want t omigrate our database to sql 2016 on different server and in order to perform the same we need to upgrade native client also but we are unable to found sql natvi client 2016 . please suggest. could we use any older version of nativ client than SQL 2016 ?

 Thank in advance.

Munna yadav.

 

Hi Munna,

It appears that there is no sql native client 2016:

"Microsoft SQL Server Native Client 11.0 is installed when you install SQL Server 2016.  There is no SQL Server 2016 Native Client. For more information, see SQL Server Native Client.  You can also get sqlncli.msi from the SQL Server 2012 Feature Pack web page."

Please see this link for more details:

https://docs.microsoft.com/en-us/sql/relational-databases/native-client/applications/installing-sql-server-native-client

Hope this helps,

Steve

Hi Steve,

Thank you for reply but i have found some articles describing that we ahve to use same version of native client with respect t oSQl database (installed on remote host). 

 

could i use sql 2012 Native client to connect to Sql 2016 databse, please confirm.

 

i have found one article ,given below...plses echeck

 

https://www.symantec.com/connect/forums/installation-sepm-database-sql-2014-what-tools-required

 

You will have to just install the SQL 2014 native client on your SEPM server for the SEPM to communicate with the SQL 2014 DB.

Any version of native client will work regardless of what SQL version you have in the backend. I believe 2012 is the latest available version that contains a native client. You can download from this link: http://download.microsoft.com/download/F/E/D/FEDB200F-DE2A-46D8-B661-D019DFE9D470/ENU/x64/sqlncli.msi

There is not native client is availble for Sql 2016 and as per Symantec artcle and i ahve rasie ticket also , Native client version should be same to Sql database installed on remote host.

Like you said. SQL 2016 is supported by SEPM, but there is no native client for 2016. Only option then is to use 2012 native client. The native client is only used to make an OCDB connection to the sql server. I have customers running 2005 native client against a 2016HA SQL cluster without issues. Probably migrated close to 20 different environments to newer SQL servers without replacing the native client. It will work :)

Hi All,

 

We have migrated / upgraded our Sep sql database from SQL 2008 t oSQL 2016 SP1 without upgrading Sql native client (bcp.exe) and everything is working fine. no issue reported.

 

 

Issue resolved...  we can upgrade databse without native client version upgrade also !

thanks all.

 

Great !

Thnaks a lot, awaiting for the above information. actually i had also tested with Sql 2008 native client with SQl 2016 databse (on remote host) and it was working on UAT server  but having some hesitation to apply in production hence raised this query.

so we can continue with old version of native client also !

 

Thank alot@TORB.