On Stop Behaviors

Previous Member
Previous Member
500 Up Votes 500 Likes 500 Comments Second Anniversary
in Platform

Hi,

 

Does anyone have a definitive guide or understanding of how the different procedure 'on stop' behaviors work? I am most interested in understanding the implications of "Must be executed until the end." My current issue is that, if a procedure is running and a data reader kicks off (even in another database), the procedure stops, with the message that it failed due to "frozenprocedures.dbo" I am wondering if i can force the procedure to wait to continue by choosing a different 'on stop' behavior. Any thoughts are appreciated.

Answers

  • Björn Reuber
    Björn Reuber Employee, Community Captain
    500 Likes Fourth Anniversary 100 Comments 5 Answers

    Hi,

     

    if you run a Procedure on DB A, this shouldnt be affected on a Procedure on DB B. Maybe there is a different problem.

     

    I think the best way would be to create a TK for this case and discuss it with our Support Team

     

    Regards

    Björn

Categories