On Cumulative Updates and GDRs
Using a fictitious future timeline, I explain how CUs and GDRs differ and why build number alone might not tell the whole story.
Using a fictitious future timeline, I explain how CUs and GDRs differ and why build number alone might not tell the whole story.
In this article, I discuss several advantages to maintaining a technical blog.
I talk about a few of the things I worked on in my first month as a DBRE at Stack Overflow.
In this tip, I show some real-life reasons why you may not want to create all the partitions you'll ever need up front.
I talk about why I prefer CONVERT over CAST to be consistent. Basically, if you sometimes HAVE to use only one, why not just ALWAYS use that one?
A new build is available for SQL Server 2019 (GDR = 15.0.2095.3, CU = 15.0.4236.7). From the CVE: "An authenticated attacker could exploit the vulnerability by executing a specially crafted query using $ partition against a table with a Column Store index."
A new build is available for SQL Server 2017 (GDR = 14.0.2042.3, CU = 14.0.3445.2). From the CVE: "An authenticated attacker could exploit the vulnerability by executing a specially crafted query using $ partition against a table with a Column Store index."
A new build is available for SQL Server 2016 SP2 and SP3. From the CVE: "An authenticated attacker could exploit the vulnerability by executing a specially crafted query using $ partition against a table with a Column Store index."
A new build is available for SQL Server 2014 SP3. From the CVE: "An authenticated attacker could exploit the vulnerability by executing a specially crafted query using $ partition against a table with a Column Store index."
There are often multiple ways to express a query and get the same results, often without any change in performance. Learn about one example.
In this tip, I talk about the compatibility between major versions and SQL Server's internal database version.