You must use Database Manager to upgrade the database in the following case:

• A version of JP1/Software Distribution Manager is to be upgraded

For details about how to upgrade a database, see 7.5.4 Upgrading the database in the manual Setup Guide.

We recommend that you make a backup of your relational database before you upgrade it. For details about making a backup, see 5.3 Backing up and restoring the system

If the relational database has become fragmented due to addition, change, and deletion of managed data, the database's data storage efficiency becomes poor. To maintain operational efficiency, you should reorganize the relational database periodically.

For details about how to check for fragmentation of a relational database and how to reorganize a relational database, see the RDBMS documentation.

JP1/Software Distribution Manager provides functions for repairing a database that has lost logical integrity and for recovering a database from a failure.

Usually when a relational database failure occurs, the database is recovered automatically by rollback. If the database is not recovered automatically for some reason, you must use Database Manager to effect recovery.

Note that Database Manager can be used to recover only Microsoft SQL Server relational databases.

For details about how to recover a database, see 7.5.5 Recovering the database (Microsoft SQL Server) in the manual Setup Guide.

When a host is deleted, its inventory information may remain in the database. This can occur when a file is used to update system configuration information. Such inventory information wastes available database space because it will not be used in JP1/Software Distribution.

You can delete such unneeded inventory information from Database Manager in the batch mode. For details about how to delete unneeded inventory information, see 7.4.8 Deleting unneeded inventory information from the database in the manual Setup Guide.

Unneeded inventory information results in the following cases:

• A file was created to update the system configuration and the hosts that were not specified in the file were deleted.
• A host was deleted from the System Configuration window, but its related inventory information was not deleted.
• Inventory information was reported from a host that is not in the system configuration.

If you have deleted many hosts, a large amount of unneeded inventory information might remain in the system. In such a case, we recommend that you delete the unneeded inventory information.

You can use Database Manager to delete inventory information for hosts that are not in the system configuration, as shown in the following table.

Table 5-3 Inventory information that is deleted

Classification	Inventory item
System information	System information
	Registry information
Software information	Installed package information
	Software inventory information
	Anti-virus product information
	Microsoft Office product information
User inventory information	User inventory information