Versions Compared

Old Version 3

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 4

changes.mady.by.user Nadja Pollard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Database availability
  • Logical fragmentation level
  • Parallel processor availability
  • Page compaction
  • Can you stop and restart the process without losing data?
  • Can you untangle interleaved indexes?
  • Is additional disk space available in the data file?
  • Is the index large?
  • Do you need to rebuild statistics?
  • Should busy pages be skipped?

Reorganize

Directs SQL Defrag Manager to defragment the tables and indexes online. This defragmentation can be stopped without losing progress. The amount of log space used varies with the amount of work completed. During reorganization, SQL Defrag Manager skips pages that are in use. In general, select this defragmentation type when the instance or database must be available during defragmentation or when you defragment a small index.

Rebuild

(SORT_IN_TEMP) directs SQL Defrag Manager to defragment the tables and indexes offline by completely rebuilding the indexes. This defragmentation type requires sufficient free space on your server and the amount of log space used can be extensive in full recovery mode. On large, fragmented indexes, this defragmentation type is significantly faster than a reorganization. In general, select Rebuild when it is acceptable that the database is unavailable during the time that the indexes are rebuilt.

Rebuild - ONLINE (SQL 2005 SQL 2005 Enterprise and later)

Directs SQL Defrag Manager to defragment the tables and indexes online by completely rebuilding the indexes. This defragmentation type requires greater resources such as disk space, memory, and processing. Because of the additional operation time and resource consumption, rebuilding online is only recommended when availability is important.

...