The Databases tab of the console allows you to manage PPM databases.
The Current Database table displays information about the current PPM database. PPM works with only one database at a time.
The Other Databases table lists all the databases that were added to PPM. To add a database to the table, refer to Adding a Database.
When a database is selected, its connectivity description appears in the Description field. Using this field, you can determine if this database can be accessed by PPM and, if PPM cannot connect to this database, the description field will specify the reason.
You can perform the following operations on the selected database:
- Cleanup: opens the Data Cleanup utility. This utility removes old data from your current database, including any number of designated old categories and sub-items. Specify a date in the Data older than field to remove unwanted data before that date while preserving any newer data after that date. The utility also includes options for removing sub-items by type. In the Data Cleanup utility, click the Run Cleanup button to activate the process.
- Remove: removes the selected database from the databases list. Note that this action does not remove the database itself from the server machine.
- Upgrade: upgrades the selected database to the latest version. You are strongly advised to backup the database before proceeding with this option.
Note: In scaled-out configurations, upgrade should be performed only on one server. Make sure all the other servers are stopped before performing the upgrade.
- Report: displays the upgrade log for the selected database.
- Make Current Database: replaces the database in the Current Database table, making the selected database the new current database. When you select this choice, you are requested to confirm stopping and restarting of PPM. If the selected database is an old version, it will be upgraded to the current version; however you are strongly advised to backup the database before proceeding.
Notes:
- In scaled-out configurations, perform this on all servers, as follows:
- Stop all servers, starting with the back-end server.
- Perform Make Current Database.
- Proceed with the front-end servers, performing Make Current Database on each, making sure to select the same database on all servers. - Since only one Primary Back-End server may use a given database at a time, you may receive a warning message when making a database Current. It explains that the database was previously used by a different Primary Back-End server. If you really wanted to switch the Primary Back-End server that uses this database, proceed by clicking OK. Otherwise, click Cancel.
- In scaled-out configurations, perform this on all servers, as follows: