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 the process of normalization?

0 Answers  

---

What is the meaning of lock escalation and why/how to stop this? : sql server database administration

0 Answers  

---

What are the steps you will take to improve performance of a poor performing query?

1 Answers  

---

what is the difference between openrowset and openquery?

0 Answers  

---

Can group by and orderby be used together?

0 Answers  

---

How to list all triggers in the database with sys.triggers in ms sql server?

0 Answers  

---

What is a self join in sql server?

0 Answers  

---

How to define output parameters in stored procedures?

0 Answers  

---

What action plan is preferred if sql server is not responding?

0 Answers  

---

Describe in brief system database.

0 Answers  

---

how we can use a database with php.

2 Answers   HCL, IT Solution,

---

What is user defined datatypes and when you should go for them?

0 Answers  

---