Does disabling triggers count as schema change in SQL Server? I am getting error: “Could not complete cursor operation because the table schema changed”
I have a stored procedure p_DeleteA that deletes a row from table A and all of its child records from table B; however, as a row in the table B gets deleted, grandchild records in table C, D, and E gets deleted as well. The above is implemented by cursor around table B where AId = xyz, then calls p_DeleteB, which deletes C, D, and E records, then B.
In the development database, the procedure works fine. However in the build environment the above mentioned error occurs. The only thing that I could image that count as “schema change” is the fact that triggers are being disabled to avoid stepping on to each other on table B. Does disabling triggers count as schema change? If not, what could cause the error message assuming that I am not changing schema in the middle. Autoshrink, which I read can cause this error, is turned off.
Edit: I am emulating cascade deletion, but I am manually deleting all records.
Development environment version: 9.00.4035.00
Build environment version: 9.00.1399.00
Yes. A trigger create/drop/alter is a schema change on the table and will trigger recompilation and invalidate dynamic cursors.