Meaning
Database maintenance requires complete rebuilding of pointer tables while the primary application remains offline. When a cold re-indexing occurs, the database engine locks the tables to prevent concurrent writes and reads, ensuring absolute consistency at the cost of immediate availability. This operation corrects structural drift.
Execution Cost
Infrastructure requirements scale with the size of the record sets being processed. A cold re-indexing demand involves high central processor utility and intensive storage read-write cycles, restricting concurrent administrative actions. Calculations of the time required must account for disk throughput limit constraints.
System Halt
Application downtime is the unavoidable consequence of blocking table access. During the period when cold re-indexing runs, user transactions are rejected or queued in a temporary buffer. For businesses with constant transactional needs, this suspension requires careful scheduling during low-traffic windows.
Operational Risk
Data corruption risks rise when unexpected hardware failures interrupt long-running operations. If the power fails before the new index is fully written, the existing pointer tables may become unreadable, leaving the system in an inconsistent state. To mitigate this, administrators maintain full offline backups before initiating the process.
Recovery from a failed attempt can take twice as long as the original scheduled window.