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!

Comments

Post a Comment

I Post più popolari

SQL Server, execution plan and the lazy spool (clearly explained)

Image
Hi Guys, Welcome back! In one of the last posts we talked about Table Spool . We had explained what Spool are for by telling the somewhat curious story of the halloween problem . Here we specifically talked about a type of spool called Eager Spool   You can look to the execution plan below where the eager Spool is used to avoid the halloween problem in classic query of the "salary increase".. i suggest Well, if the story of the eager spool intrigued you, today instead we will speak about another type of Spool, the Lazy Spool . The Lazy spool Let's take a small step back. So, what is a Spool operation?  As we have already understood a spool operation is simply a temporary storage of data . Data are read from a source table and stored inside a worktable in the Tempdb database . While an Eager Spool is used to prevent the Halloween problem, the Lazy Spool is instead used to store data that will later be needed again when running a query . So, when a Lazy spool is used?  ...
Read more

SQL Server, datetime vs. datetime2

Image
Hi guys, This time, in this post we will speak about datetime and datetime2 datatypes. We will talk about the pros and cons. We will talk about all the differences between the two types of data. Write me in the comments which type of data do you prefer between the two. Enjoy the reading!     Datetime Vs. Datetime2 First of all, it must be said that the datatype datetime is certainly the best known native format for storing a date in SQL Server. However, Microsoft has also been introducing a new type of data for many years now, also used to manage dates. It is in fact from SQL server 2008 that it is present in datetime2 data type. This "new" type of data was born primarily to have higher accuracy . Let's in fact talk about ... precision ! Datetime Certainly the datetime data type is not very precise and certainly there are many cases in which its precision is simply not sufficient. Let's see it with an example. Open the SQL Management studio (SSMS) and write the fo...
Read more

La clausola NOLOCK. Approfondiamo e facciamo chiarezza!

Image
Ehi ragazzi! La domanda è di quelle importanti! Siete pronti per scoprire tutto ma proprio tutto sulla clausola NOLOCK?   Se la riposta è si, allora seguitemi! Oggi ne spiegheremo il funzionamento in maniera approfondita. Faremo una introduzione al concetto di tipi di LOCK Ed infine vedremo come mai una SELECT ne può bloccare un'altra. Non vi nascondo che il motivo di questo articolo è fare chiarezza. Su questo argomento si sentono spesso affermazioni “curiose” ma tra le tante questa è la prima: “ uso la SELECT con l’opzione WITH(LOCK) così non blocco le altre tabelle ”.   Ma, è proprio vero quanto affermato? Beh oggi facciamo il punto!   Buona lettura!     La clausola NOLOCK Diciamo subito per iniziare che cos’è la NOLOCK. NOLOCK è il nome di una clausola che è possibile specificare all’interno di uno statement di tipo SELECT utilizzando la seguente sintassi: SELECT * FROM TABELLA WITH (NOLOCK) Si noti che non possiamo ...
Read more