T-SQL Tuesday #151 : Controversial Coding Conventions
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?
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."