TLS 1.2 support on SQL server 2014
We have SQL server 2014 (with sp3 installed) hosted on Windows Server 2012 R2. Recently our client application upgraded to use OpenSSL 3.0.8 and we are restricting to use TLSv1.2 & TLSv1.3 only. Now our client application is not able to connect to SQL server via ODBC driver 17/18. I tried enabling TLSv1.2 on SQL server 2014 including applying service pack3 (https://support.microsoft.com/en-us/topic/kb3135244-tls-1-2-support-for-microsoft-sql-server-e4472ef8-90a9-13c1-e4d8-44aad198cdbe), updating host OS, updating .NET on host OS, adding registry entries to Schannel, enabling group policy to use FIPS enabled ciphers, etc. Unfortunately none of these solved the issue. I tried to diagnose the issue with openssl/sslscan utilities, but they are also not able to connect to the server on port 1433. Client waits for 'server hello' during handshake and timeout happens. The Windows/system log shows the errors: 1. 36874 : An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed. 2. 36888: A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The windows schannel error state is 1205. Note that, same client can connect to another instance of SQL server 2016 hosted on another server without any issue. Could you please suggest what more configuration we are missing on SQL server 2014?
How Get Application name in a Login Failure
Group How could I get the name of an application, in a login failure, by SQL Server. Where normally the error code would be Login failed for user '(???)'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>] Error: 18456, Severity: 14, State: 8.Performance issue in Production box
Hi Folks, I have one query which will give only 192 records from database tables. In that query multiple SQL views are used. When I am executing that query in Production it is taking 3 mins but when I execute the same query on test environment it is executing in 1 second. To further drill down the issue I ran the execution plan in production box I am getting index scan and no parallelism but in test environment i am getting Index seek and parallelism. all the SQL server properties and database properties are same in production and test box. Please help me to under the issue. Regards Sachin Goel
List all permission on server role and database role on sql server 2014
Hello All, On our organization , we are on the way to apply SoD (Segregation of duties) between system and security admins so we want to list all permission on server role and database role hints 1- We know that that there is security admin role 2- I googled about to list all permission on server role and database role but with no luck Thanks in AdvanceSharePoint 2019 with SQL Server 2014 SP1
Can SharePoint 2019 use SQL Server 2014 SP1? https://docs.microsoft.com/en-us/sharepoint/install/hardware-and-software-requirements-2019 lists Minimum requirements for a database server in a farm One of the following: Microsoft SQL Server 2016 RTM Standard or Enterprise Editions Microsoft SQL Server 2017 RTM Standard or Enterprise Editions for Windows SharePoint Servers 2016 and 2019 Databases technical diagram seems to suggest SQL Server 2014 SP1 can be used http://download.microsoft.com/download/7/9/7/79700E8E-9896-4657-B9E6-4940B295B71A/DBrefguideSPS2019_tabloid.pdfLesson Learned #28: Why does SQL SERVER Management Studio report that my Azure SQL Database version is 12?
First published on MSDN on Aug 07, 2017 Very often, our customers are asking about why does SQL Server Management Studio report that my Azure SQL Database versions is 12? Does it mean that I'm using SQL SERVER 2014? Why does it mean that is not updated?The explaination is that if your application check the version of SQL using select @@version the information reported will be wrong, because, right now, to identify the version of Azure SQL Database, we use the combination of edition and ProjectMayorVersion ( select SERVERPROPERTY('edition'), select SERVERPROPERTY('ProductMajorVersion').
