Database index for single instancing

The Single-Instance feature requires an index to be manually created in the database. In a scenario without partitioning the SQL statement to create this index looks as shown below.

Oracle and PostgreSQL

create index IDX_ARCH_PHYSICAL_F_HASH on ARCH_PHYSICAL_FILE (FILE_HASH_DIGEST ASC, PARTITION_KEY ASC);

MS SQL server

create index [IDX_ARCH_PHYSICAL_F_HASH] on [ARCH_PHYSICAL_FILE] ([FILE_HASH_DIGEST] ASC, [PARTITION_KEY] ASC);

If the database tables are partitioned, an additional clause for the appropriate index space or partitioning setup must be appended to the statement. This can best be found by examining an already existing index from the ImageMaster database model in the target database.

If the index is not available, a log message with level SEVERE (with id IMA9_INV_01020) is written to the ImageMaster.log. This index is not included in the standard database model to avoid taking up a large amount of index space, which is unnecessary if the feature is not used.