Partitioning strategy

The present chapter includes information on partitioning strategies based on DB2 and Oracle. Partitioning in SQL Server is configured differently: the actual partition scheme is not defined in the ImageMaster configuration, but rather directly in the database using the partitioning function. For related details see chapter Partitioning in Microsoft SQL server .

The queries of the ImageMaster system are designed in such a way, that a partitioning criterion is included if possible. For this reason the database model has the column “partition_key” in all document related tables. The content of this column is the same in all rows of each table of one respective document. It is determined depending on the document to be archived. It should be assured that all revisions and the content objects of one document have the same value for the column.

A partitioning procedure offers three fundamental data distribution methods as basic partitioning strategies that control how data is placed into individual partitions. ImageMaster supports the following strategies1 For each of the above mentioned partitioning strategies a license must be obtained from the database provider. depending on the database system:

Partitioning Strategy	Oracle	PostgreSQL2 Partitioning requires at least PostgreSQL 10 as database version.	SQL Server
List	ü	ü
Range	ü	ü	ü
Hash	ü	ü
Table 387: Partitioning strategy/database compatibility