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 a performance monitor?

0 Answers  

---

Explain identity in sql server?

0 Answers  

---

What command is used to create a database in the sql server and how?

0 Answers  

---

What method is used by the Command classes to execute SQL statements that return single values?

0 Answers   B-Ways TecnoSoft,

---

Explain time data type in sal server 2008?

0 Answers  

---

what is a major difference between sql server 6.5 and 7.0 platform wise? : Sql server database administration

0 Answers  

---

How to create a new schema in a database?

0 Answers  

---

What are the dmvs?

0 Answers  

---

How to use union to merge outputs from two queries together in ms sql server?

0 Answers  

---

What is an expensive query?

0 Answers  

---

How do I create an extended event in sql server?

0 Answers  

---

What are key, name and value columns of an attribute? : sql server analysis services, ssas

0 Answers  

---