• LutzM (5/21/2011)


    Based on the code in the sproc you posted:

    This is designed to do the same sort of thing as Access's cascade delete function.

    Why don't you add a (referential) foreign key constraints with a cascade delete instead of trying to rewrite a functionality that's already there?

    See BOL, section "FOREIGN KEY Constraints" for details.

    (Added hyperlink to above...)

    You'll have to implement this with CREATE TABLE or ALTER TABLE

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes


    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2