lock time out is untrappable in TSQL 
Author Message
 lock time out is untrappable in TSQL

The following run-time error occurs correctly during an update statement
when Table1 is being held in another transaction:

UPDATE Table1 SET Col1 = 'abc'
(lock time out occurs)

Server: Msg 1222, Level 16, State 50, Procedure pUpdateSomething, Line 53
Lock request time out period exceeded.

It seems SQL shuts down all subsequent processing after the UPDATE

lock time out is ignored. Our client code receives the error, but we would
like to use our home-grown TSQL Application Event Logging procedures.

If this is by design, are there other SQL run-time errors that also behave
like this?

(SQL 2000)

TIA,
John



Sat, 15 Nov 2003 12:11:11 GMT
 lock time out is untrappable in TSQL

Found the fix.

http://support.microsoft.com/support/kb/articles/Q286/2/86.ASP



Sat, 15 Nov 2003 12:40:56 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. 1222 (lock time out) is untrappable

2. Continual time-outs (time is not on my side)

3. Paradox lock files and kick outs

4. Time Outs in JDBC

5. MS SQL Server 2000 time-outs periodicly over the internet

6. Time-outs

7. Performance trouble, time outs

8. Setting Time Outs

9. Time outs

10. MS SQL Server 2000 time-outs periodicly over the internet

11. SQL Server ODBC connection time-outs?

12. query time outs! please help


 
Powered by phpBB® Forum Software