SQL Server 2017 Cumulative Update #31 is available, with 24 enhancements. The build number is 14.0.3456.2. This is the last mainstream cumulative update for SQL Server 2017!

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

SQL Server 2017 Cumulative Update #29 is available, with 18 enhancements. The build number is 14.0.3436.1.

SQL Server 2017 Cumulative Update #28 is available, with 10 enhancements. The build number is 14.0.3430.2.

SQL Server 2017 Cumulative Update #27 is available, with 14 enhancements. The build number is 14.0.3421.10.

SQL Server 2017 Cumulative Update #26 is available, with 31 enhancements. The build number is 14.0.3411.3.

SQL Server 2017 Cumulative Update #25 is available, with 19 enhancements. The build number is 14.0.3401.7.

SQL Server 2017 Cumulative Update #24 is available, with 30 enhancements. The build number is 14.0.3391.2.

SQL Server 2017 Cumulative Update #22 is available, with 42 enhancements. The build number is 14.0.3356.20.

SQL Server 2017 Cumulative Update #21 is available, with 35 enhancements. The build number is 14.0.3335.7.

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 2017 Cumulative Update #20 is available, with 40 enhancements. The build number is 14.0.3294.2.

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.

SQL Server 2017 Cumulative Update #19 is available. The build # is 14.0.3281.6 and there are 38 fixes.

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

I start a series looking at using clustered columnstore indexes and page compression to address storage footprint for a 1TB table.

Updated for a more modern version, I explain how to install and use SQLLocalDB.