The following applies to upgrades starting on schema versions prior to 7.5.0.0.
To facilitate the process of upgrading the IN_DOC table in uptime, a copy of the IN_DOC table is created during setup and is synchronized with the original table until the downtime steps have completed. This requires that additional storage be allocated to the database filegroups to accommodate the copy of the IN_DOC table and its indexes.
Before executing the UPGRADE and SYNC setup commands you will want to ensure that you have sufficient free space in the database filegroups where the new version of the IN_DOC table and indexes will be created. You can use SQL Server Management Studio (SSMS) to get the current size of the IN_DOC table (Data space) and its indexes (Index space) by completing the following steps.
Within SSMS, follow these steps to find the minimum amount of storage required for the upgrade.
- Within the Object Explorer window, navigate to the IN_DOC table.
- Right click on the IN_DOC table and select Properties.
- Select the Storage page.
- Under the General section, you will find the current size in MB.
- Data space will reflect the current size of the IN_DOC table (PK_DOC clustered index)
- Index space will reflect total size of all the non-clustered indexes on the IN_DOC table.
Additional storage considerations
- The Data and Index space collected above represents the current size. Consideration should also be given to additional storage to accommodate the expected volume of new documents created during the period of time that the synchronization process is in place.
- If you are currently using the default FILLFACTOR of 100% (also represented as 0) and planning to create the new indexes using a non-default FILLFACTOR size (<100%) then you will need to add a proportionate amount of storage to account for the extra pages required to hold the same amount of data. For example, if you set fillfactor to 95%, resulting in leaving 5% of each page empty and free to accommodate future data changes, then you will also want to increase the total size allocated by an additional 5% to account for the extra pages that would be required to store the same amount of data.
- During the downtime steps, the original IN_DOC table and indexes will be replaced by the new versions created during the uptime steps. Upon completion of the upgrade downtime steps and after the original IN_DOC table and its indexes are dropped the storage it consumed will be released and become available within the respective filegroups.
- In a default implementation, the table (clustered index) will be located in the PRIMARY filegroup and all the non-clustered indexes will be located in the SECONDARY filegroup.
- In order to reclaim the additional disk space added during the upgrade you may choose to create the new IN_DOC table and indexes in a new, temporary filegroup during the upgrade and move them at a later time, after the upgrade, using the online index rebuild process. Note that online index rebuilds is an Enterprise Edition feature. Once the table (clustered index) and the nonclustered indexes have been moved back to their original filegroups, and the temporary filegroup is empty, you can drop the empty filegroup and its files to reclaim that disk space.