The database upgrade process makes significant changes to the structure of the Capacity
Database. We recommend that the database is backed up before proceeding, if not done so
already. The upgrade process has paused at this point to provide the opportunity to take
a backup if required.
Figure 1. Upgrade Database - warning about the need for a backup
- Click No to halt the database upgrade process, so that a backup can be performed and then re-run the upgrade process.
- Click Yes to proceed with the upgrade.After clicking Yes, a number of progress indicators are displayed while the Upgrade Database determines what changes are needed. (e.g., “Loading foreign keys for table36/66”). A list of changes that need to be made to your database will be displayed once this dialog box completes.Figure 2. Upgrade database - List of changes to be applied
Note: The version and revision numbers of the existing and new databases are dependent on the Syncsort™ Capacity Management fix level and may be different as shown. - Click OK to commence upgrading the Capacity Database.Some progress messages while the database is being upgraded will be displayed. (e.g., “Executing SQL statement 635/5870”)Dependent on the database size and type of data stored, the upgrade process could take anywhere from several minutes to hours. Once completed, the message confirming that the database has been upgraded is displayed, as shown below.
- Click Exit to complete the Upgrade Database process.Note: Once the Upgrade Database process has completed, it is possible that some high levels of CPU utilization for the SQL Server system that hosts the Capacity Database will occur. This may happen when a SQL Server index change has been made in Upgrade Database and SQL Server subsequently updates all the index entries as a background task. Once the index updates have been completed then the CPU usage levels will fall back to their normal levels.
This elevated CPU usage is therefore, an expected result of running Upgrade Database in such circumstances. Do not attempt to throttle the CPU usage by SQL Server as this could severely degrade the throughput of Syncsort™ Capacity Management data processing.