EDIT#3 SQLOLEDB and the SQL Server ODBC driver (part of MDAC, shipped and serviced with Windows) has support for TLS 1.2 with October 20, 2020 build, version 17763.1554. This applies to Windows 10 and Windows Server 2019 or later.
Update: SQL Server 2016 will have native JSON support - a new JSON datatype (which is based on nvarchar) will be introduced, as well as a FOR JSON command to convert output from a query into JSON format
As of April 2024, Azure SQL Database has now (finally) added support for "real" Regular-Expressions using the POSIX dialect (as opposed to the PCRE or .NET Regex dialects, oddly); it is currently in Preview, so enabling this feature requires you to opt-in via a sign-up form and pray to Satya that your request is approved).
Our primary focus for SSMS 21 was to move to Visual Studio 2022, provide initial support for SQL Server 2025 Preview, and support the Copilot in SSMS Preview. Our team is actively working to bring these features back in an upcoming release. For now, if you rely on SSIS we recommend using SSMS 20, which you can install side-by-side with SSMS 21 GA.
In PostgreSQL there is the Limit and Offset keywords which will allow very easy pagination of result sets. What is the equivalent syntax for SQL Server?
SQL_Latin1_General_CP1_CI_AS breaks up into interesting parts: latin1 makes the server treat strings using charset latin 1, basically ascii CP1 stands for Code Page 1252 CI case insensitive comparisons so 'ABC' would equal 'abc' AS accent sensitive, so 'ü' does not equal 'u' P.S. For more detailed information be sure to read @solomon-rutzky's answer.
SQL Transaction Error: The current transaction cannot be committed and cannot support operations that write to the log file Asked 14 years, 2 months ago Modified 1 year, 8 months ago Viewed 259k times
I want to store a large n-dimensional vector (e.g. an embedding vector) in SQL Server as a piece of metadata associated with another row. In this example, it will be a 384-dimensional vector, for e...
I have one SQL Agent maintenance job which checks the index fragmentation within a database and rebuilds indexes if required. This is running well in my test server (Microsoft Sql Server 2012). But...
