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

If we shrink the Databse and Files, how much size is decreased?

1 Answers   TCS,

---

List all the types of user-defined functions?

0 Answers  

---

How to use the inserted and deleted pseudo tables?

0 Answers  

---

Explain triggers?

0 Answers  

---

how will add additional conditions in sql?

0 Answers   Amdocs, Apps Associates,

---

What happens when transaction log is full?

0 Answers  

---

What do you mean by stored techniques? How would we use it?

0 Answers  

---

What is deadlock and how to avoid the deadlocks.

3 Answers   TCS, Wipro,

---

What is the simplest way to create a new database in ms sql server?

0 Answers  

---

What is the difference between a function and a stored procedure?

0 Answers  

---

What are the new scripting capabilities of ssms? : sql server management studio

0 Answers  

---

Name three of the features managed by the surface area configuration tool? : sql server security

0 Answers  

---