What is the prefered method to do cascading updates and deletes in a SQL Server database? Are they best done with triggers, stored procedures, or is there some database setting to tell the database to perform cascading deletes over the whole system?
Printable View
What is the prefered method to do cascading updates and deletes in a SQL Server database? Are they best done with triggers, stored procedures, or is there some database setting to tell the database to perform cascading deletes over the whole system?
Not sure about Sql Server 7.0 but in 6.5 if you want cascade deletes you have to write them yourself. Which method should you use to implement? Triggers. They're, ulitmately, faster and more tightly coupled with the data.
John's right, especially when you're working in a perfect world. Unfortunately, I've found in large multi-user production environments, I more often have to settle for second best and use the stored procedures route instead.