2.2.2 Existence of usage of table partition functionality

(1) Examining usage method of table partition functionality

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

Table 2‒3: Relation of table partition functionality and the database to be used

Usage method of table partition functionality	HiRDB Server		Other DBMS
	HiRDB/Single Server	HiRDB/Parallel Server
Partition by date data (month)	Y	Y	N
Partition by date data (month) and also to manage by distributing in multiple servers	N	Y#	N
When table partition functionality is not used	Y	Y	Y

To Page Top

(2) Examining table partition configuration

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?)

To Page Top

(3) HCSC server setup

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 "6.4.3 HCSC server setup definition file" in "Service Platform Reference Guide".

To Page Top