Hello Sanjeev, I am able to reproduce this error too. I assume this error occurs because Toad set chained on when you launch debugger but the transaction mode in which you created this procedure is unchained. You can check this status via value of column sysstat2 from dbo.sysobjects. 0 means unchained, 16 means chained while 32 represents anymode. One solution to ths problem is you can run sp_procxmode to change the mode of procedures you want to debug to anymode: sp_procxmode procedure_name, "anymode" Afterwards, please try debugging again and see if you still come across this error. Thanks, Charon.
↧