Posted by pb648174 on 10/01/89 11:43

The whole cascading delete issue is a major pain in the ass that I
can't believe MS didn't fix in SQL 2005. If we can manually write
triggers to do so, the SQL Server should just be able to handle the
*possibility* of cascading paths and just throw an error when there
actually *were* cascading paths.

• Next in forum: Re: Multiple Foreign Keys on Same Table
• Prev in forum: LDAP authentication for Yellowfin on SQLserver
• Thread view: Re: Multiple Foreign Keys on Same Table

[Reply to this message]