On page “General” (figure 7-1) a path to files of the current GDB is indicated. The page contains a table where in column “Size” there are sizes of all GDB files separately, by three databases and the total sum. In the column “Maximum size” it is shown which sizes can files have with the current page sizes. In the column “Ratio (%)” percentage ratio of the current page sizes to maximum sizes is shown. If this ratio is close to 100 percent, it is recommended for the user to increase the page sizes.
Figure 7-1. GDB property sheet, page “General”
If the box Show details of using files is checked two more columns will be filled: the column “Used” containing the size of useful data in files and the column “Filled (%)” with a ratio (in per cents) of the used data volume to complete file sizes (figure 7-2).
Figure 7-2. Page “General” with the details of using files
On the basis of the information about GDB size and filling, decisions about performing reorganization of this GDB are taken.
Below you will find a list of recommendations how to take this decision. They are based on the knowledge of inner data structure and experience in working with ObjectLand.
If the total size of data files of each of three databases (definitions, tables and maps) does not exceed several hundreds of kilobytes then reorganization is inexpedient not depending on the percentage of filling. If some of these files reaches several megabytes or more, see next points.
If the percentage of filling data file from any of the tree databases is less than 50 it is necessary to perform reorganization.
If the percentage of filling index file of table or map area is less than 25 then reorganization should be performed.
Filling definitions files is not taken into account.
So, if the GDB size is small, low filling percentage should not be considered abnormal. It makes sense to obtain more dense filling only for big, “megabyte” GDB.
 |  |
