SQL SERVER, One thing you should definitely know about the UPDATE statement ...

Hello friends,

Today, waiting for the saturday, we talk about a simple thing that you really should know about the UPDATE statement.

How many times have you seen updates done like this? 

 

       
UPDATE ORDRIG

SET

  NeatPrice = Price * (100-PercDiscount)/100,

  total = NeatPrice * Qty

where

  id = XX

 

Notice that the result of the second field depends on the result of the first one.
So in this case order matters.

How does SQL Server behave in this case?

Seems difficult but it is more easy than you could image!
 

Just learn this easy rule:

The UPDATE does not see the results of its work.

 

Of course you can tray by yourself doing this simple update:

CREATE TABLE #ORDRIG (ID INT IDENTITY(1,1), PRICE FLOAT, NETPRICE FLOAT)

INSERT INTO #ORDRIG (PRICE,NETPRICE) VALUES (0,0)

UPDATE #ORDRIG SET PRICE = 5, NETPRICE = PRICE


SELECT * FROM #ORDRIG


 




Et voilà!

That's all for today
I wish you a great saturday!
Luca











Previous post:SQL Server, How to execute T-SQL commands from the command line (attention this post may contain easy but useful tips 😏 )

Comments

  1. James ZicrovDecember 19, 2020 at 4:01 AM

    I feel SQL is actually a sophisticated and vivacious tool to look for whenever one needs to find out solutions to database related operations.Kudos to the blogger for putting this up.

    SQL Server Load Rest API

    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?    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