This error occurs if there is a delete trigger on the table which causes another action - e.g. another insert, update, or delete - which causes another trigger or procedure to be called and that trigger/procedure causes another action to occur which causes another trigger/procedure to be called and that trigger/procedure causes another action to occur which .... etc, etc, etc ... until the nesting of calls to triggers or procedures is so deep that the database server go no longer processs the trigger/procedure call.
i.e. you have a run-away recursion in one of your (delete) triggers on the table.
For example, does your delete trigger attempt to delete another row in the same table? (which would then fire the trigger again!)
To resolve the problem, you need to first find the source of the recursion and then determine a way to stop the recursion before the nesting goes too deep.
answered 03 Apr '10, 23:02