5.3 Running the database

If the number of Operational Contents increases and the number of nodes per Operational Content is greater than planned, the database size specified during the setup stage might no longer be adequate. You can solve this problem by periodically checking the database usage status and re-evaluating the database size that is needed.

The database size specified during setup assumes that Operational Contents are created under the following conditions.

Table 5‒1: Operational Contents that can be created with the database size specified at setup
No.	Item	Expected value
1	Number of Operational Contents	500
2	Average number of nodes per Operational Content	20
3	Average number of items that are placed in a flow area	30
4	Average number of items that are placed in a Guide area	35
5	Average number of plugin items associated with an Operational Content^#	20

#: Sum of System Plugins and User Plugins.

The following figure shows the general procedure for running a database.

Figure 5‒1: General procedure for running a database

Even if you have created Operational Contents within the limits of the database size specified at setup, periodically check the database's usage status and extend the database's size before all available space is depleted.

You use Navigation Platform commands to check the database usage status and extend the database size.

Organization of this section

To Page Top