It is painful that...

I can’t get anyone to kill a SQL Server process that is blocked.

It was 10:00 MST when I 1st put in a ticket that I had a database performance issue.

It was 2:30 MST when I updated the ticket that it was a single table that was unselectable.

It was 4:00 MST when I went through chat and gave the SQL statement that showed that I had a blocked process since 6:30 in the morning. I gave permission to kill all my processes. ( 20 of them are blocked now )

4:30 MST I put that same information into the ticket in hopes it would prompt someonen to kill the processes.

It is now 5:15 MST and the processes are still not killed.

100 clients down which is bad enough but having them still down after knowing what the problem is ( but not being able to fix it myself) is painful.

Andy

Thank you whoever went in and killed the processes.

Andy

Andy,

This is on VPs or shared? We have one staff out today and that is in the windows team, I am busier than busy in preps for moves and had no clue of this pending.

It isn’t an excuse or anything, but killing SQL processes is generally something we don’t train just everyone out of the box. Sorry for the delay.

The database itself was on shared ( although used by my reseller account and my VPSs) so I went through the shared support.

I was just frustrating to take a day off work to diagnose the problem and then when I finaly did not be able to do anything about it myself.

I’ll have to try to come up with a backup plan for next time.

I gave you one in PM :slight_smile: