The following table describes the relation of table partition functionality and the database to be used:

Table 2-3 TableRelation of table partition functionality and the database to be used

(Legend)

Y: Can be executed.

N: Cannot be executed.

Note #

HiRDB Advanced High Availability Version 9 is required for use.

While using table partition functionality, examine data volume of 1 month (potential value) on the basis of the following points and decide the partition configuration:

• How many back-end servers are to be used?
• Data of which month is to be compiled and handled?
• How many months are to be used as units for circulation? (Data of how many months is to remain in the database?)

When table partition functionality is used, definition as follows is required in HCSC server setup definition file:

db-tbl-split-key=MONTH
db-tbl-split-corcheck-use=ON
sql-scriptfilename=Path of SQL script file defining table partition#

Note #

This definition is required when the 1^st HCSC server in a cluster is setup.

Since creation of the table, index and view table that are the targets of table partition functionality is complete during the 1^st HCSC server setup, SQL script file need not be created for HCSC server setup from the 2^nd server onwards.

For details on SQL script file, see "Appendix D.2(2) Renaming RD Areas or table areas".

For details on HCSC server setup definition file, see "HCSC server setup definition file" in "Service Platform Reference Guide".