DBCC INDEXDEFRAG 1

[icemel]

From BOL:

"Unlike DBCC DBREINDEX (or the index building operation in general), DBCC INDEXDEFRAG is an online operation. It does not hold locks long term and thus will not block running queries or updates."

Has anyone else used this and can verify that the above statement is true and does not cause performance problems?

Thank you

 

[SQLDenis]

DBCC INDEXDEFRAG does a large number of mini transactions and the tables are available while when you reindex the table is not available, that said DBCC INDEXDEFRAG will make your log file grow (a lot sometimes)

I have jobs running on weekends that defragment large(170 million records) tables without a problem, you can stop it anytime and it will pick up where it left of last time



“I sense many useless updates in you... Useless updates lead to defragmentation... Defragmentation leads to downtime...Downtime leads to suffering..Defragmentation is the path to the darkside.. DBCC INDEXDEFRAG and DBCC DBREINDEX are the force...May the force be with you" --

http://sqlservercode.blogspot.com/