Re: Error -710: Table has been altered, rename or drop

In <01bb89f1$dbea2720$6b65a8c6@telecom.int>, Telecom wrote: >Does enybody have some cues to fix this problem. The problem raise >ramdonely. To fix the problem presently, we rerun the stored procedure >or querie 2 or 3 times and finaly we get the result. If you get error 710, it is no wonder you are getting the problem now and then, because altering a table which is being referenced directly or indirectly ( by envoking a trigger which references the table ), in stored procedure will mismatch the procedure's optimization to the structure of the table. When you get the error the procedure will reoptimize with the current structure of the table, and next time the procudure will run fine. Another alteration to the table will again mismatch the procedures optimization and then re-optimize, making the error intermittent. You should take a close look at what is being done to the table-schema, if whatever is being done is really necessary then do an UPDATE STATISTICS / UPDATE STATISTICS FOR PROCEDURE proc_name, which will reoptimize the procedure synchrinizing the table-schema and the procedure optimization. -- Have a nice day Felix K. Mathews mailto:fmathews@systems.dhl.com