Database Storage for the IN_INSTANCE_PROP Indexes - Database Storage for the IN_INSTANCE_PROP Indexes - Perceptive Content - Perceptive Content Database Upgrade Package for SQL Server - Perceptive-Content/Perceptive-Content-Database-Upgrade-Package-for-SQL-Server/Foundation-26.1/Perceptive-Content-Database-Upgrade-Package-for-SQL-Server-Reference-Guide/Prerequisites/Database-Storage-for-the-IN_INSTANCE_PROP-Indexes - Foundation 26.1 - Foundation 26.1

Perceptive Content Database Upgrade Package for SQL Server Reference Guide

Platform
Perceptive Content
Product
Perceptive Content Database Upgrade Package for SQL Server
Release
Foundation 26.1
License
ft:lastPublication
2026-04-16T22:28:17.811000
ft:locale
en-US
The following applies to upgrades starting on schema versions prior to 7.4.0.3.

To accommodate the uptime creation of the new filtered indexes on the IN_INSTANCE_PROP table, additional storage will need to be allocated to the respective database filegroup. The new filtered indexes will be created in addition to the existing indexes to ensure proper index coverage. Once all the new indexes have been created, the existing non-filtered indexes will be automatically dropped.

You can use SQL Server Management Studio (SSMS) to get the current size of the IN_INSTANCE_PROP indexes (Index space) by completing the following steps.

Within SSMS, follow these steps to find the minimum amount of storage required for the upgrade.

  1. Within the Object Explorer window, navigate to the IN_INSTANCE_PROP table.
  2. Right click on the IN_INSTANCE_PROP table and select Properties.
  3. Select the Storage page.
  4. Under the General section, you will find the current size in MB.
  5. Index space will reflect total size of all the non-clustered indexes on the IN_INSTANCE_PROP table.
  6. For additional storage considerations, the Index space collected above represents the current size of the indexes. Consideration should also be given for storage to accommodate the expected volume of new documents or custom properties created during the period of time when the new indexes are being created and before the existing indexes are dropped.
  7. In a default implementation, all the non-clustered indexes are located in the SECONDARY filegroup.