But the transaction that xp_cmdshell did was quite small: just creating a test file. it should have taken less than a second to roll it back.
Will killing the explorer.exe from task manager help here?
This is a known issue with killing any spid. If it has 0% to go but stays there, check to see if it's using CPU time. If it's not, just ignore it and the next service bounce will take care of it. It it is using CPU time, try to find the spid the actual xp_CmdShell command used (tougher than it sounds) and kill that. Doing so will resolve the other 0% rollback spid.
Otherwise, like I said, it's a known problem and it's going to take restarting the service to take care of the problem.
And, no... don't ever kill explorer.exe from Task Manager.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs