|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Today @ 6:40 AM
Points: 3,619,
Visits: 1,229
|
|
sqlpro (11/9/2009) thanks for the reply. probably i misunderstood but following is the link i got my understanding from.its here http://www.informit.com/library/content.aspx?b=STY_Sql_Server_7&seqNum=145
Careful. You are quoting from a book that is over ten years old. This is usually fine if the book is about theoretical or academic work but that book is a "Teach Yourself To Be A Dummy In 60 Seconds" styled book on SQL Server 7.
I know some people may still be supporting SQL Server 7 installations. I know that a lot of people like these types of books.
I only said be careful.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 4:53 PM
Points: 7,182,
Visits: 7,281
|
|
A really nice article. Good explanation.
Tom
Tom Is minic a gheibheann béal oscailte dorn dúnta. Is minig a cheapas beul fosgailte dòrn dùinte.
http://es.linkedin.com/in/tomthomsonsoftware
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Wednesday, July 25, 2012 3:23 AM
Points: 18,
Visits: 126
|
|
| Enforcing delete cascade will also help here, instead of creating indexes. I believe it should eliminate the deadlock. Of course if you enable delete cascade it's no point in deleting from child table first and then parent table. We have to do just a delete from parent table.
|
|
|
|