Frage

I have a loooooong running script that us generating a clustered index on a 77M row - 20GB table.

I need to query this data so I want to stop the Index Generation and resume it in the night.

Is it OK to KILL the ProcessId?

War es hilfreich?

Lösung

SQL Server should respond just fine to killing any process. However, it might take a while to cleanup after itself. For instance, if you kill a big update query, it will have to roll-back the transaction. For in index build, it should not have such problems and should return relatively quick. Point is, as long as you let the kill finish without doing something drastic like powering down, you should be fine.

Andere Tipps

Killing the PID will cause the transaction to roll back.

It shouldn't hurt to do, but the rollback is going to be painful.

There is no way to pause it and continue later where you left off.

Lizenziert unter: CC-BY-SA mit Zuschreibung
Nicht verbunden mit StackOverflow
scroll top