SQL Server 2019 CU11 is out! ....and again on Scalar UDF Inlining

Hi Guys,

The SQL Server CU 11 is out. 

Looking to the Microsoft changelog there aren't great imprevements from point of view of the performance, but from what i can see there is another update on the "Scalar UDF Inlining" saga!

We talked about Scalar UDF inlining here: SQL Server, boost your UDFs!

Yes i really think that UDF inlining (debut with SQL Server 2019 in order to increase performance) will became an important technology but what is happened unfortunately is a little different.

Due to errors, at each CU Microsoft restricted the action and the functionality of the Inlining..

For example in the CU2 inlining is blocked if the UDF references built-in views (for example . OBJECT_ID) or when aggregate functions are passed as parameters to a scalar UDF. Again if the UDF references certain intrinsic functions (for example @@ROWCOUNT.

Updating to the CU4 inlining is blocked if the UDF uses XML methods or contains a SELECT with ORDER BY without a "TOP 1" and even if the SELECT query performs an assignment in conjunction with the ORDER BY clause (for example, SELECT @x = @x +1 FROM table ORDER BY column_name)

And so on CU after CU..

I think that probably the internal logic inside this concept is not again mature, but at last microsoft shows that he wants to continue on this path!


and now CU 11 and inlining

Also this latter CU has its new cases where the inlining is blocked. 

Inlining is blocked if the UDF references encrypted columns or  to 'WITH XMLNAMESPACES' or if the query invoking the UDF has a CTE.


SQL Server 2021

By the Way, the first  rumors are already being heard about the new SQL Server 2021!Who guesses in which month it will be announced?



That's all for today my friends!  

Have a great week and share knowledge!!!

Luca Biondi @ SQLServerPerformance blog 2021!


Previus post:How to change Sql Server name. A micro tips!

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?    I
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 utilizzare questa cl
Read more