Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32)

  • I have a Stored Procedure and getting a Error

    "Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32)".

    Please help.

  • It means you're calling a procedure, view or function from your procedure, and then from that proc calling another, etc 32 levels deep. Or it could be recursive with the proc calling itself.

    Either way, you're going to have to track down where that is coming from and change the code so that the nesting level isn't anywhere close to that deep. There's no way to change the maximum nesting level.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • In my SP, I'm trying to delete the No. of rows on the basis of some conditions.

    So, that query is acting as recurssive. Is there a way to change that option.

  • shishir999_ril (3/23/2009)


    In my SP, I'm trying to delete the No. of rows on the basis of some conditions.

    So, that query is acting as recurssive. Is there a way to change that option.

    That shouldn't be a recursive query unless you're explicitly calling a function from within itself. Post the query please?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • I would put $ on it being recursive because there is a trigger on that table that edits/deletes other records in the table that then fire the trigger, etc. etc.

  • Please note: 2 year old thread.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Hi,

    Looks like my question is related to this thread.

    I am trying to delete some rows in parent table and related rows in child tables. I am using below sp, but throwing error. Please help me to update the sp so that I can delete all related tables rows.

    error:

    Msg 217, Level 16, State 1, Procedure spDeleteRows, Line 58

    Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).

    CREATE Procedure spDeleteRows

    /*

    Recursive row delete procedure.

    It deletes all rows in the table specified that conform to the criteria selected,

    while also deleting any child/grandchild records and so on. This is designed to do the

    same sort of thing as Access's cascade delete function. It first reads the sysforeignkeys

    table to find any child tables, then deletes the soon-to-be orphan records from them using

    recursive calls to this procedure. Once all child records are gone, the rows are deleted

    from the selected table. It is designed at this time to be run at the command line. It could

    also be used in code, but the printed output will not be available.

    */

    (

    @cTableName varchar(50), /* name of the table where rows are to be deleted */

    @cCriteria nvarchar(1000), /* criteria used to delete the rows required */

    @iRowsAffected int OUTPUT /* number of records affected by the delete */

    )

    As

    set nocount on

    declare @cTab varchar(255), /* name of the child table */

    @cCol varchar(255), /* name of the linking field on the child table */

    @cRefTab varchar(255), /* name of the parent table */

    @cRefCol varchar(255), /* name of the linking field in the parent table */

    @cFKName varchar(255), /* name of the foreign key */

    @cSQL nvarchar(1000), /* query string passed to the sp_ExecuteSQL procedure */

    @cChildCriteria nvarchar(1000), /* criteria to be used to delete

    records from the child table */

    @iChildRows int /* number of rows deleted from the child table */

    /* declare the cursor containing the foreign key constraint information */

    DECLARE cFKey CURSOR LOCAL FOR

    SELECT SO1.name AS Tab,

    SC1.name AS Col,

    SO2.name AS RefTab,

    SC2.name AS RefCol,

    FO.name AS FKName

    FROM dbo.sysforeignkeys FK

    INNER JOIN dbo.syscolumns SC1 ON FK.fkeyid = SC1.id

    AND FK.fkey = SC1.colid

    INNER JOIN dbo.syscolumns SC2 ON FK.rkeyid = SC2.id

    AND FK.rkey = SC2.colid

    INNER JOIN dbo.sysobjects SO1 ON FK.fkeyid = SO1.id

    INNER JOIN dbo.sysobjects SO2 ON FK.rkeyid = SO2.id

    INNER JOIN dbo.sysobjects FO ON FK.constid = FO.id

    WHERE SO2.Name = @cTableName

    OPEN cFKey

    FETCH NEXT FROM cFKey INTO @cTab, @cCol, @cRefTab, @cRefCol, @cFKName

    WHILE @@FETCH_STATUS = 0

    BEGIN

    /* build the criteria to delete rows from the child table. As it uses the

    criteria passed to this procedure, it gets progressively larger with

    recursive calls */

    SET @cChildCriteria = @cCol + ' in (SELECT [' + @cRefCol + '] FROM [' +

    @cRefTab +'] WHERE ' + @cCriteria + ')'

    print 'Deleting records from table ' + @cTab

    /* call this procedure to delete the child rows */

    EXEC spDeleteRows @cTab, @cChildCriteria, @iChildRows OUTPUT

    FETCH NEXT FROM cFKey INTO @cTab, @cCol, @cRefTab, @cRefCol, @cFKName

    END

    Close cFKey

    DeAllocate cFKey

    /* finally delete the rows from this table and display the rows affected */

    SET @cSQL = 'DELETE FROM [' + @cTableName + '] WHERE ' + @cCriteria

    print @cSQL

    EXEC sp_ExecuteSQL @cSQL

    print 'Deleted ' + CONVERT(varchar, @@ROWCOUNT) + ' records from table ' + @cTableName

    --delete a row, example

    exec spDeleteRows 'X', 'field1 = ''234''', 0

  • It's worth to notice that laddu4700 already posted his question in a different thread.



    Lutz
    A pessimist is an optimist with experience.

    How to get fast answers to your question[/url]
    How to post performance related questions[/url]
    Links for Tally Table [/url] , Cross Tabs [/url] and Dynamic Cross Tabs [/url], Delimited Split Function[/url]

  • Thanks for this suggestion, I had a similar problem and i was able to resolve it after removing a proc call within the same procedure. Now it's not throwing any error when executing the proc.

    :hehe:

  • pleas i have the same prob pleas write the procedure after modifying

  • CAN SOMEONE tell me what is wrong with this code

    I have two tables LicParcela, and LicKo , I want, when i Draw ( insert) new Parcela ( Polygon type), to check in With LiKo (Polygon) is, and to give LicParcela.LicKoId that Id of LicKo

    CREATE TRIGGER ubacujeKoIdZaParcelu

    ON dbo.LicParcela

    AFTER INSERT,UPDATE

    AS

    BEGIN

    DECLARE @C int

    SET @C=(SELECT LicKo.LicKoId FROM LicKo,LicParcela

    WHERE LicKo.geom.STContains(LicParcela.geom)=1

    )

    UPDATE LicParcela

    SET LicParcela.LicKoId=@c

    END

    GO

  • This was removed by the editor as SPAM

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply