|
-
Aug 17th, 2000, 11:42 AM
#1
Thread Starter
Member
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?
-
Aug 17th, 2000, 12:50 PM
#2
Frenzied Member
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.
-
Aug 17th, 2000, 09:41 PM
#3
Hyperactive Member
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.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|