SQL Server Native Client 11.0 vs SQL server DRIVERS
I have a web application with a MS SQL 2012R2 Server in the back end.
If we connect to the server with our connection string using "SQL Server" then the system works fine, but we cannot disable TLS 1.1 because apparently this driver uses that version.
If we connect to the server using SQL Server Native Client 11.0 then we can disable TLS 1.1 and use TLS 1.2 only, BUT then certain fields from our database such as text fields, nvarchar(max), and apparently any long strings won't work anymore. The data is not displayed in the ASP files and some other errors are displayed in the application.
What is causing this with the 11.0 connection and how can we fix it?
If we connect to the server with our connection string using "SQL Server" then the system works fine, but we cannot disable TLS 1.1 because apparently this driver uses that version.
If we connect to the server using SQL Server Native Client 11.0 then we can disable TLS 1.1 and use TLS 1.2 only, BUT then certain fields from our database such as text fields, nvarchar(max), and apparently any long strings won't work anymore. The data is not displayed in the ASP files and some other errors are displayed in the application.
What is causing this with the 11.0 connection and how can we fix it?
Qlemo
Can you show the connection string? I cannot see any reason for what you describe, as the Native Client supports more datatypes and features directly.
You may need to upgrade your SNAC version.
Which one do you have (check in the Add/Remove programs)?
Which one do you have (check in the Add/Remove programs)?
ASKER
There are a lot of programs and patches installed. How do I know which one to check?
I understand the sql 11 native should support better, but as I mentioned we have issues in the application if we use it.
I understand the sql 11 native should support better, but as I mentioned we have issues in the application if we use it.
ASKER
There is one entry that reads "Microsoft SQL 2012 Native Client"
date: 05/18/2017
ver: 11.3.6518.0
That is the only Native client listed in the programs install/uninstall list
date: 05/18/2017
ver: 11.3.6518.0
That is the only Native client listed in the programs install/uninstall list
I'm only talking about SNAC (SQL Server Native Client). Other programs are irrelevant.
This is what you should see and have for working properly:
This is what you should see and have for working properly:
ASKER
Yes, it is there and my prev. post has the version.
So you already have the latest patch.
Does that server has the WannaCry patch installed (check in the Windows Update for KB4012212)?
Does that server has the WannaCry patch installed (check in the Windows Update for KB4012212)?
I'd start checking the "MS SQL 2012R2 Server in the back end' service pack and install the latest
ASKER
I dont see those patches installed. Could that cause the issue when using the native driver 11 ?
ASKER
BTW, this is a VM in Azure, not sure they allow us to see the patches or if they this on their end. I am just getting familiar with the platform.
In which server are you checking those patches?
SNAC version should be checked in the Web App server.
WannaCry patch should be checked in both servers (Web App and SQL Server).
SNAC version should be checked in the Web App server.
WannaCry patch should be checked in both servers (Web App and SQL Server).
ASKER
SNAC I checked on the web server. I don't manage the SQL server. As I mentioned this is hosted in Azure Cloud. And I did not see that patch or any other patch on the web server for that matter. I am not sure if they do this on their end and I can't see it. Ill ask.
How would that prevent us from using TLS 1.2 and Native Driver 11 ?
How would that prevent us from using TLS 1.2 and Native Driver 11 ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK. So we can't disable TLS 1.1 under Azure environment and have to connect using 1.1 ?
If I disable 1.1 then the connection fails (1.2)
If I disable 1.1 then the connection fails (1.2)
ASKER
I have TLS 1.0 disabled. But we are trying to disable 1.1 so that it forces the use of 1.2 only.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Will do. thanks for the help.