SQL Server 2022 Gets Its 2nd Update in 2 Days

It never rains but it pours, right? Tuesday, we got a GDR, and today, we get Cumulative Update 1. Microsoft’s makin’ up for lost time!

Some of the fixes include:

• Fixes an issue with differential backup skipping new Page Free Space (PFS) pages after a data file grows around a PFS boundary (a multiple of 8,088 pages; 64,704 KB), resulting in database corruption and a possible crash dump when this differential backup is restored.
• This update removes the requirement for the trace flag (TF) 809 for the hybrid buffer pool with direct write feature. After you apply this update, this feature is enabled by default in SQL Server 2022.
• Improvement: The sp_invoke_external_rest_endpoint stored procedure is only supported in Azure SQL Database environments.
• Fixes an issue where the read query on a readable secondary replica may be aborted or return unexpected results if the query uses a heap and forwarding records are present in the heap.
• Access violation occurs when temporary tables are invoked inside UDFs by using synonyms (added in Microsoft SQL Server 2022 CU1 and SQL Server 2019 CU19)
• Fixes an issue where an authenticated attacker could affect SQL Server memory when executing a specially crafted CREATE STATISTICS or UPDATE STATISTICS statement.
• Fixes a gradual memory leak in the SQL Server process (the high usage under MEMORYCLERK_SOSNODE) caused by the Log Reader Agent in transactional replication.
• This fix is a safeguard for issues that can cause unavailability due to memory capacity in some rare queries (nested queries performing table scans).
• FIX: Database accessibility issues with high-volume customer workloads that use EKM for encryption and key generation
• Adds the queries and category of the Microsoft Customer Experience Improvement Program (CEIP) telemetry to SQL Server 2022.

And much, much more. Go get ’em! Odds are, there won’t be another update tomorrow. (The day after that, well, it’s anybody’s guess.)