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

Is it possible to run multiple publications and different type of publications from the same distribution database? : sql server replication

0 Answers  

---

What are different types of raid levels?

0 Answers  

---

Write the syntax for stuff function in an sql server?

0 Answers  

---

What is the use of “join” in sql server?

0 Answers  

---

What is row_number()?

0 Answers  

---

Can we rollback records deleted by a truncate statement?

3 Answers   CarrizalSoft Technologies, United Healthcare,

---

Does server sql treat char as a variable-length or fixed-length column?

0 Answers  

---

You have a table with close to 100 million records recently, a huge amount of this data was updated now, various queries against this table have slowed down considerably what is the quickest option to remedy the situation?

0 Answers  

---

Can a stored procedure call itself or recursive stored procedure? How many levels sp nesting is possible?

0 Answers  

---

between cast and convert which function would you prefer and why?

0 Answers  

---

Explain about Normalization?

0 Answers   Infosys,

---

What is difference between stored procedure and function?

3 Answers   L&T,

---