Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

While trying to update a table definition (change a field type from NVARCHAR(5) to NVARCHAR(8)) we caused a lock on the database. There were a large number of rows (>11,000,000) so we decided to kill the process and roll back the update.

During the rollback the status of the process was showing as 'sleeping' with a Wait Type of IO_COMPLETION or PAGEIOLATCH_EX.

How can I give the KILL/ROLLBACK process a higher priority and prevent it going to sleep?

share|improve this question
up vote 2 down vote accepted

ROFL, wouldn't it be great if assigning a greater priority to a process will make your hardware faster? Both of your wait types are due to IO subsystem not keeping up. You'll just going to have to wait it out.

share|improve this answer
OK, thought it was probably going to be something like that. I think we had something else going on with the server at the time which was causing it to slow down generally. Sorry for the silly question and thanks for explaining the wait types were due to hardware. – Swinders Jan 26 '11 at 9:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.