Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-12-27 : 11:46:59
|
| dev_null writes "As a long term solution would you reccemmend using cascade deletes to manage your records in an enterprise level database. I don't think it is a good idea because I see it as limiting your flexability. On the other hand I don't want to be closed minded. I don't have a specific example in mind, I'm just speaking from a general design perspective.thanks" |
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-12-27 : 12:42:09
|
| I don't believe it's a good idea either. One of your primary design goals should always be simplicity, and clarity of purpose. A DELETE statement that does more than delete from the referenced table causes headaches for everyone on your team. It's a source of bugs and it goes against the concept of referential integrity.Jonathan{0} |
 |
|
|
|
|
|
cascade deletes