Comments on: SQL SERVER – Basic Explanation of Query Hint NOWAIT – How to Not Wait on Locked Query

By: praveen

praveen — Fri, 01 Feb 2013 06:36:50 +0000

hi pinal i have used same query in first window with small change like
BEGIN TRAN
DELETE FROM First
WHERE ID = 1
COMMIT

but after running this am executing same code in second window but still getting same errror..any comments on this

By: SQL SERVER – Difference Between NOLOCK and NOWAIT Hints « SQL Server Journey with SQL Authority

Fri, 01 Feb 2013 01:30:27 +0000

[...] Basic Explanation of Query Hint NOWAIT – How to Not Wait on Locked Query [...]

By: pinaldave

pinaldave — Tue, 29 Jan 2013 04:03:39 +0000

Thanks for pointing it out.
Fixed!

By: rainmaker

rainmaker — Tue, 29 Jan 2013 03:30:37 +0000

Pinal: Use NoWait or SET SET LOCK_TIMEOUT. (double SET?)
should change to
Pinal: Use NoWait or SET LOCK_TIMEOUT. ?

By: SQL SERVER – Basic Explanation of SET LOCK_TIMEOUT – How to Not Wait on Locked Query « SQL Server Journey with SQL Authority

Mon, 28 Jan 2013 01:31:04 +0000

[...] earlier blog post SQL SERVER – Basic Explanation of Query Hint NOWAIT – How to Not Wait on Locked Query, we learned how we can use NOWAIT query hint to not wait on any locked query and return error. The [...]

By: pinaldave

pinaldave — Sun, 27 Jan 2013 10:24:13 +0000

Excellent note Prasanna!

By: rohitmssqlfun

rohitmssqlfun — Fri, 25 Jan 2013 19:16:33 +0000

Nice one.

By: BANAZ GHAZI

BANAZ GHAZI — Fri, 25 Jan 2013 17:26:06 +0000

hi I want design form in access and source for form is two table and these tables existed in sql server 2008 please answer me

________________________________

By: amar gupta

amar gupta — Fri, 25 Jan 2013 09:59:19 +0000

Very Thnks 2 u Pinal, nice article , i am so happy to Learn New Feature of SQL.
now waiting (Lock_TimeOut)

By: Prasanna Peshkar

Prasanna Peshkar — Fri, 25 Jan 2013 06:52:41 +0000

Nice post . This is similar to Oracle. in Oracle, In For update nowait the rows will busy and acquire lock until any commit or rollback is executed. Other session try to aquire the lock will
get a oracle error message like ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired instead of waiting the lock to release.
Session1:
SQL>select * from dept where deptno =10 for update nowait;

Session2:
SQL>select * from dept where deptno =10 for update nowait;
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired.

That means NO_WAIT Specifies that if the changes in the database cannot complete immediately without waiting for transactions to commit or roll back on their own, then the request will fail.