SQL Server concurrency problem, select after update, to avoid the concurrency of dirty read resolution

In SQL Server, the data operation needs to be followed by a select Update, which, if high concurrency occurs, can cause dirty reads to occur. Data synchronization is not guaranteed.

The solution is to add an update lock to the table in the thing:

Transaction one:

begin Tran Declare @count int =0Select @count=[Count]  fromTb_name with(UPDLOCK,HOLDLOCK)whereId=1Select @count  asCount1waitforDelay'00:00:30'UpdateTb_nameSet [Count]=@count+1 whereId=1Commit Tran  Select *  fromTb_name

Transaction two:

begin TranDeclare @count int =0Select @count=[Count]  fromTb_name with(UPDLOCK,HOLDLOCK)whereId=1Select @count  asCount2UpdateTb_nameSet [Count]=@count+1 whereId=1Commit Tran  Select *  fromTb_name

SQL Server concurrency problem, select after update, to avoid the concurrency of dirty read resolution