DotNetKicks.com - Stories tagged with Locks

SQL Server 2005: Immediate Deadlock notifications

Wed, 21 May 2008 17:48:15 GMT

Deadlocks can be a pain to debug since they're so rare and unpredictable. The problem lies in repeating them in your dev environment. That's why it's crucial to have as much information about them from the production environment as possible. This is one way of getting it immediatly when it happens,

SQL Server 2005: Get full information about transaction locks

Wed, 07 May 2008 03:16:03 GMT

Get information about what locks are being held by the transaction, what SPID owns the transaction, on which objects the locks are being held, what SQL statement caused the locks, etc...

SQL Server 2008: Locking with MERGE statement compared to Update/Inser

Fri, 03 Aug 2007 19:30:52 GMT

How SQL Server 2008 MERGE statement locking compares to the locks held when doing "update if exists, insert if not" problem in SQL Server 2005.

SQL Server: Best way to Update row if exists, Insert if not

Wed, 01 Aug 2007 19:01:02 GMT

This question pops up a lot everywhere and it's a common business requirement and until SQL Server 2008 doesn't come out with it's MERGE statement that will do that in one go we're stuck with 2 ways of achieving this. The biggest problem with every update/insert (upsert for those who haven't heard the term yet) is locking.