Answer / jay

Below is a quick recipe for a dead lock. Two transactions,
one first updating table 1, then 2 and the other one doing
it in reverse order.

Both transactions wait in the middle for 20 seconds to give
you some time to execute them 'simulaneously'.

When you run the two in transactions in two windows 'at the
same time', you'll only have to wait ~20 seconds, and one of
the windows will experience a dead lock.




CREATE TABLE t1 (i int);
CREATE TABLE t2 (i int);

INSERT t1 SELECT 1;
INSERT t2 SELECT 9;


/* in one window enter: */
BEGIN TRAN
UPDATE t1 SET i = 11 WHERE i = 1
WAITFOR DELAY '00:00:20'
UPDATE t2 SET i = 99 WHERE i = 9
COMMIT

/* in a second window (another transaction) enter: */
BEGIN TRAN
UPDATE t2 SET i = 99 WHERE i = 9
WAITFOR DELAY '00:00:20'
UPDATE t1 SET i = 11 WHERE i = 1
COMMIT

What is normalization process?

0 Answers  

---

What is partition, how will you implement it? : sql server analysis services, ssas

0 Answers  

---

when you create a database how is it stored? : Sql server database administration

0 Answers  

---

how many type of subquery?

2 Answers  

---

Do you know what guidelines should be followed to help minimize deadlocks?

0 Answers  

---

How many levels of sp nesting is possible?

0 Answers  

---

Where does the copy job runs in the log shipping primary or secondary? : sql server database administration

0 Answers  

---

How many types of indexes are there in SQL Server?

6 Answers   CarrizalSoft Technologies, United Healthcare,

---

Using query analyzer, name 3 ways you can get an accurate count of the number of records in a table?

5 Answers   eFunds,

---

What are the new features in SQL Server 2005 when compared to SQL Server 2000?

0 Answers  

---

What are the advantages of having an index on the sql server?

0 Answers  

---

What is the server name in sql server?

0 Answers  

---