Procedure errors out but SPID stays in sysprocesses

  • HI All

    Have any one of you faced a scenario where the procedure is aborted because of error/lost connection or any other reason but the spid that it used stays in sysprocesses table?

    The issue that I am facing is 1 start 5 threads of same proc using SSIS but once in a while what is happening is that one of the session gets killed. But I still see that sysprocesses table has the spid of that proc.

    Can some specific severity level error cause this?

     

     

    Online Trainer For SQL DBA and Developer @RedBushTechnologies with 18 yrs exp.

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

Viewing 2 posts - 1 through 2 (of 2 total)

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