SQL Server 2022 and the GENERATE-SERIES command .. a T-SQL language enhancement

Hi Guys,


Welcome back!

I have to admit that I like to find out what is added in each new version of SQL, especially the T-SQL language part.
There will be a lot to talk about ..

So let's start!
Today we see the first improvement of T-SQL language that the new SQL Server 2022 bring us: the GENERATE_SERIES command


The GENERATE_SERIES command

I bet that when we are asked to generate a series of numbers such as 1,2,3, .. or 2, 4,6 etc etc immediately we think of the CTE (the well-known "common table expression") or the function of ranking ROW_NUMBER.

Someone then invents some more original but still functional approach.

Let's see some ways currently used to generate a series of values:

Using a CTE:


WITH Cte AS 
(
  SELECT 1 AS x
  UNION ALL 
  SELECT x + 1 FROM Cte WHERE x < 5
)
SELECT * FROM Cte  -- remember to add the option maxrecursion...

Executing this command we will have:


 

Or we could use a ranking function:


SELECT ROW_NUMBER() OVER (Ordery by object_id) FROM sys.objects

In this case, it is necessary to rely on the rows of an existing table (which must have a sufficient number of rows)

At this point the new command comes into play!

Just type:


SELECT * FROM GENERATE_SERIES ( START = 2, STOP = 12, STEP = 2 )

...et voilà!


You can avoid to explicit that name of the parameter ( START, STOP, ETC..)


Speaking of performance!

We run a very simple benchmark generating a series of number from 1 to 1000 to compare the execution time of the two solution: GENERATE_SERIES Vs. CTE approach!

The execution time of the new GENERATE_SERIES command is twice as fast as with the CTE solution. 2015 ms Vs. 4334 ms!

Another aspect is the CPU time. The new command is a clear winner whit 47 ms. Vs. 3215 ms!




That' all for today!

Stay tuned for the next posts ... others new T-SQL commmands will follow soon...
But please follow me on linkedin!

Luca









Previous post:SQL Server 2022 and the Parameter Sensitive Plan Optimization (PSP) with example

Comments

  1. alinaAugust 3, 2022 at 3:32 AM

    Once you've chosen how often you'd like to receive these LinkedIn emails, you can choose to receive them at all or just the weekly digest. If you're interested in new profiles or are searching for a job opportunity, you might prefer the Weekly Digest. To know more about email finder, check here.

    ReplyDelete

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