What is the effect of DBCC CHECKDB and DBCC DBREINDEX on the Transaction log?
Question: On our SQL Server 2000 system every Sunday early hours we have a scheduled job to execute the database optimization tasks such as DBCC DBREINDEX and DBCC CHECKDB which is running without any problems. But during this time we are getting errors and alerts about user database transaction log is out of free space. What is the impact on the transaction log for executing the DBCC DBREINDEX and DBCC CHECKDB? Answer: As you may be aware DBCC DBREINDEX can be used to rebuild one or more indexes for a specific table and it is an offline operation. While this operation is running, the underlying table is unavailable to users of the database. DBCC DBREINDEX rebuilds indexes dynamically. During this operation it restores the page density levels to the original fillfactor (default); or the user can choose another target value for the page density. Internally, running DBCC DBREINDEX is very similar to using TSQL statements to drop and re-create the indexes manually. Internally DBREINDEX pr
