SQL Server, use transactions in a smarter way. The save transaction

Hi Guys,

Today we will talk more about transactions...

Oh no, not again! I am hearing some of you are saying  …you have already explained it yesterday!

Yes exactly but today's post is lighter and in just 5 minutes we see how to use transactions in a smarter and more flexible way!

Ready!


What?

 

 

 

 

 

SQL Server, such as Oracle and others RMDBS, allows you to associate a name with a transaction and even allows to you to perform a partial rollback! 

If you think about it, having the ability to open a transaction and at the end of a procedure to commit or rollback alltogheter is a bit limiting.

For example, in case you have to go back to the beginning of the whole procedure, which may be very long.

 

Between Save Transaction and Partial Rollback

SQL Server provides this two commands: 


 

SAVE TRANSACTION transaction_name
ROLLBACK TRANSACTION transaction_name

 

Where transaction_name is the name of the transaction.

With the SAVE TRANSACTION <tran> you can save a precise point in the transaction.
 
With the ROLLBACK TRANSACTION <tran> you can rollback your data to a precise point you saved.

 

EXAMPLES

 

A) In this first example, i execute a procedure "first_part_of_the_procedure" that update my data.

At this point i save my transaction with the name "first_update_done".

Then i execute another procedure called "Second_part_of_the_procedure". If i get an error i rollback not all the entire transaction but only to the first_update_done point.

When i execute the commit my data have been updated by the first_part_of_the_procedure.


B) Second example 
 
In this case i have a simple table. 
I insert a row and i save the transaction with the name FirstInsert.
Then i insert another row and i save the transaction again but with the name SecondInsert.
Then i insert another row but execute the rollback to the savepoint SecondInsert.
Doing the commit e then a select of my table i have 2 rows!


That's all for today.

I hope you enjoyed the article!
Remeber to share knowledge!!!
Luca Biondi @ SQLServerPerformance blog 2021!


Previus post:SQL Server: Transactions, Lock e Deadlock. A little bit of theory explained in a simple way!

 



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