Kill DBCC Reindex?

Can anyone explain what happens if you kill a dbcc
reindex command (all indexes)?DBCC DBREINDEX is one transaction, and when you kill a process, the
transactions that it is running will be rolled back. So you will end up with
the same situation you had before you ran DBCC DBREINDEX, and you will
probably have to wait quite a long time (maybe the same time as DBCC
DBREINDEX has run already) for the rollback to complete.
Jacco Schalkwijk
SQL Server MVP
"Mitch" <anonymous@.discussions.microsoft.com> wrote in message
news:5d3c01c474c1$f6c40c50$a301280a@.phx.gbl...
> Can anyone explain what happens if you kill a dbcc
> reindex command (all indexes)?|||So if the process was blocking users to access a
database, and you killed the process, it just returns the
indexes back to their original form? Doesn't damage the
indexes?

>--Original Message--
>DBCC DBREINDEX is one transaction, and when you kill a
process, the
>transactions that it is running will be rolled back. So
you will end up with
>the same situation you had before you ran DBCC
DBREINDEX, and you will
>probably have to wait quite a long time (maybe the same
time as DBCC
>DBREINDEX has run already) for the rollback to complete.
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Mitch" <anonymous@.discussions.microsoft.com> wrote in
message
>news:5d3c01c474c1$f6c40c50$a301280a@.phx.gbl...
>
>.
>|||It will return the indexes to what they were before. Your users can't access
the table though while the rollback is in progress.
Jacco Schalkwijk
SQL Server MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:5e4a01c474c5$c87f45e0$a401280a@.phx.gbl...[vbcol=seagreen]
> So if the process was blocking users to access a
> database, and you killed the process, it just returns the
> indexes back to their original form? Doesn't damage the
> indexes?
>
> process, the
> you will end up with
> DBREINDEX, and you will
> time as DBCC
> messagesql