Hi,
We've got some issues with a procedure which from time to time seems to hang with the NOP command. [Seen in sysprocesses(cmd)]
Because this procedure adds data to a lot of heavily used tables it doesn't take long to lock the whole system.
The process stays and waits in this NOP state until we kill it.
The only explanation I found about this, is that it is a low-level instruction telling the processor to wait for the next cycle.
Does anyone know what this command means in SQL Server? And what could cause SQL server to hang?