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."

In this tip, I show how you can evaluate a new index option in SQL Server 2019 aimed at reducing PAGELATCH_EX waits: OPTIMIZE_FOR_SEQUENTIAL_KEY.

I like to encourage people to always be on the latest Cumulative Update, but lately my confidence has been eroding. The latest patch for SQL Server 2019 hasn't helped.

See how to work around some of the blockers for replacing legacy UDFs with STRING_SPLIT.

Cumulative Updates for SQL Server 2019, SQL Server 2017, and SQL Server 2016 SP2 have been pushed back a month or more due to our current health crisis.

SQL Server 2019 Cumulative Update #4 is available, with 50 enhancements. The build number is 15.0.4033.1.

SQL Server 2019 Cumulative Update #3 is available, with 56 enhancements. The build number is 15.0.4023.6.

In this tip, I show how to measure the positive effects of delayed durability, in cases where a small amount of data loss is acceptable.

It's a few days later than many of us were expecting, but Cumulative Update #2 for SQL Server 2019 (15.0.4013.40) is overflowing with 134 fixes and enhancements.

SQL Server 2019 Cumulative Update #1 is now available, with 83 fixes and improvements. Build # is 15.0.4003.23.

In this tip, I show how and why a columnstore index can provide benefits to COUNT(*) queries.

Get a quick overview of one of the most important features in SQL Server 2019.

Read a quick overview Scalar UDF Inlining, a long-awaited feature in SQL Server 2019 that will improve the performance of some workloads.

This new approximate function may not cut down on execution time, but it relieves a whole lot of memory pressure.

Some of your gnarly scalar UDFs will stop being in the naughty book when they can be inlined.

New first class citizen in SQL Server 2019 that will help you identify and audit sensitive information.

This new function eliminates some of the tedious legwork you might find yourself doing with DBCC PAGE.