Very Computer

> I am looking for opinions on the issue of Referential Integrity vs Using
> Triggers to Simulate Cascade Deletes, since SQL Server 7 doesn't allow
both.
> Do you sacrifice referential integrity and use triggers - or do you
maintain
> referential integrity at the database level and use stored procedures to
> perform cascade deletes? Even though you can theoretically (with much
work)
> create enough triggers to maintain referential integrity, I have read that
> triggers are slower than using foreign key constraints.  Also, security is
> an issue since you can dissallow all deletes at the table level and only
> give permission to the stored procedure. The downside to the stored
> procedure method is the obvious "mess" it creates. This has been a huge
> company discussion and any opinions are appreciated.
> Thanks,

>Coding the cascade function in triggers or procs is about the same level of
>development effort.  I don't see procs being any messier than triggers.

>Personally, I prefer DRI and would use procs for this functionality under
>SQL 7.  Better yet, upgrade to SQL Server 2000 since it provides cascaded
>functions via DRI.

>Hope this helps.

>-----------------------