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 |
|
Quadracerke
Starting Member
4 Posts |
Posted - 2003-08-27 : 05:33:21
|
| Hi,I've just tried out the script to perform a cascade delete( www.sqlteam.com/item.asp?ItemID=8595 ) but when I try it I always get this error Server: Msg 217, Level 16, State 1, Procedure spDeleteRows, Line 58Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).Does anyone know what the problem can be?Thanks in advance,Dries Matton |
|
|
Quadracerke
Starting Member
4 Posts |
Posted - 2003-08-27 : 08:18:14
|
| Is there really nobody that can help me? I'm pretty despirate!Great thanks in advance,Dries. |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2003-08-28 : 01:56:41
|
quote: Originally posted by Quadracerke I've just tried out the script to perform a cascade delete( www.sqlteam.com/item.asp?ItemID=8595 ) but when I try it I always get this error Server: Msg 217, Level 16, State 1, Procedure spDeleteRows, Line 58Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).
Are you running SQL 2000? Cascading delete is a feature of SQL 2000 now, so if you are running SQL 2K you can just turn that option on without having to use this code.if you are SQL 7, do you have triggers on the tables you are deleting from? nr has some information on his website regarding this error and triggers (along with tons of other indespensible information, his site should be bookmarked by everyone) http://www.nigelrivett.net/BasicTriggers.htmlAlso, check out the original comments on the article http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=14594. The procedure was rewritten to use a temp table to hold the primary key values. This increases speed of the procedure and may help you out with your error as well by avoiding a bunch of nested in lists.-ec |
 |
|
|
|
|
|
|
|