If the process is originated from different machine, then using task manager and doing end process on that machine might help. Here is the query which can tell us more about the SPID and from where the connection might have originated. If the SPID is not showing any change in CPU, Memory and IO column then it is doing nothing.sys.sysprocesses DMV (query in the next step). Such SPID should show a change in CPU, Memory and IO column in size. Some large operations may take a long time to rollback. Have patience and wait for rollback to finish.There are only a few things, which you can do: How would you decide which action to take? It completely depends on the action done by the SPID which was killed. These are the cases where its stays in KILLED/ROLLBACK state forever. There are situations where SQL doesn’t know and has no control of work done of the work done and it has no control to roll back the work. Once that happen, if SQL knows how to rollback that work, it would start “real” rollback process and would undo the work done. The first question which would come to mind would be “what is killed/rollback command?” The answer is very simple – sometimes, DBA/Developer use “KILL” command to end processes that appear in a hung state. If you are a SQL DBA or developer, I am sure you must have seen something like below: Recently killed/rollback discussion came back when my close DBA friend called me for help. I always recall my fun days after talking to my friends and blog readers.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |