SQL Server 1 ways to proactively prevent blocking

Method 1,

Set LOCK_TIMEOUT 5000; This setting timeout is 5 seconds;

Example:

Connection A

BEGIN Tran
UPDATE dbo. TestTable
Set String = ' AAA '
where id=1;
Go

Connection b

UPDATE dbo. TestTable
Set String = ' BBB '
where id=1;
Go

You can see that you are not setting lock_timeout it is going to wait forever.

Connection C

Set LOCK_TIMEOUT 5000;

UPDATE dbo. TestTable
Set String = ' BBB '
where id=1;
Go

You can see that as long as the 5s timeout, the problem comes,

Is the next batch of connection C also a 5s timeout? Let's take a look.

Or 5s indicates that this set LOCK_TIMEOUT is valid for a connection, not just for a single batch.

SQL Server 1 ways to proactively prevent blocking