For some reason, one of my replication jobs got stuck at running this SP today. Now all other replication jobs trying to write to this table are waiting as my spid has placed a table lock on sysjobhistory. Needless to say, replication is not happening. The message in the Replication monitor is something along the lines of "waiting for a backend connection".
The spid got "stuck" at 1:15pm. I tried to kill it at around 2:20pm. It's now 3:50pm and it still says "KILLED/ROLLBACK" as the status. In my experience, SPID's usually rollback in about the same amount of time they have been running before being killed (tops). This one is still going strong. I have bounced the SQL Agent service and nothing has changed.
Anyone have any clues? What else can I do??
Thanks!
Craig
The spid got "stuck" at 1:15pm. I tried to kill it at around 2:20pm. It's now 3:50pm and it still says "KILLED/ROLLBACK" as the status. In my experience, SPID's usually rollback in about the same amount of time they have been running before being killed (tops). This one is still going strong. I have bounced the SQL Agent service and nothing has changed.
Anyone have any clues? What else can I do??
Thanks!
Craig