Search Suggest

SPEED NEWS! Cumulative Update 16 for SQL Server 2019 is out!

Hi Guys,

The Last SQL Server cumulative update 16 (CU16) is out!
It was officially released the 04/18/2022.
 
As usual I want to emphasize the importance of updating the product: Maybe not the same day the CU is made available but still update! 

Let's see what it contains!
Enjoy the reading.


Cumulative Update 16 for SQL Server 2019

For each cumulative update, Microsoft releases a list of the changes and corrections it makes, we can find it here

Although divided by areas and by platform, its reading is unfortunately not always very clear.

I refer to reports like this: 

"Bug reference 14522124 - Dropping temp tables in some rare cases causes an unresolved deadlock and dump"

It is not clear when the error occurs and how to reproduce it. 
Certainly, however, it is better that a problem of this type is solved.

Now let's see what we find interesting within this CU

 

Extended Event (XEvent):

A new one, named query_store_plan_forcing_user_change is added to track when the user manually force or unforce a plan for a query in the Query Store (KB 14541295)

Others two, iam_page_range_cache_invalidation and iam_page_range_cache_population are added to respectively capture Index Allocation Map (IAM) page range cache invalidation and population. (KB 14623946)

Very cool!

 

Scalar UDF Inlining

Microsoft SQL Server 2019 introduced the Scalar UDF Inlining feature. 

A great idea to improve the performance of queries that invoke T-SQL Scalar UDFs, in which UDF execution is the main bottleneck. This is because SQL Server is now able to transforms inlineable UDFs into relational expressions.

We talked about many times for example SQL Server, boost your UDFs! 

Curious the fact that CU after CU have been gradually added conditions in which this operation must not be performed because it would have given an error. Read here.

In this CU16 i can read: 

"Inline UDF function running as the non-sysadmin account could throw error 'A severe error occurred on the current command.  The results, if any, should be discarded'"

 

You can read all the CU16 log here


 That all for today!



 




The (    ) Button

Previous post: A special post: One day at work with me!

Post a Comment