Indexes and Constraints

This topic covers validations and warnings that database indexes and constraints can cause.

In this topic:

Overview

A database index is a data structure that improves the speed of operations in a table. You can create indexes using one or more columns, providing the basis for both rapid random lookups and efficient ordering of access to records. Database Constraints are constraints on the database that require relations to satisfy certain properties.

Extra Index

The OpenText Application Quality Management schema should include only those indexes defined in the required schema configurations.

Problem: If the verification process finds an index that is not defined in the required schema configuration, it generates an Extra Index warning.

Solution: Remove the extra indexes manually. Consult with your database administrator to resolve this issue. For details, see Change the database user schema.

Extra Constraint

The OpenText Application Quality Management schema should include only those constraints defined in the required schema configurations.

Problem: If the verification process finds a constraint that is not defined in the required schema configuration, it generates an Extra Constraint warning.

Solution: Remove the extra constraint manually. Consult with your database administrator to resolve this issue. For details, see Change the database user schema.

Index Uniqueness Mismatch

A unique index guarantees that the index key contains no duplicate values. As a result, every row in the table is unique. Specifying unique indexes on OpenText Application Quality Management data tables ensures data integrity of the defined columns. In addition, it provides helpful information that is used as a query optimizer.

Problem: If the index uniqueness attribute does not have the expected value, the verification process generates an Index Uniqueness Mismatch warning.

You cannot create a unique index, unique constraint, or PRIMARY KEY constraint if duplicate key values exist in the data. The verification process performs these data validations. If a table has duplicate values or IDs, based on the index definitions on that table, the verification process also displays the duplication in the verification report. In this case, the repair process automatically fixes the duplication problem before creating the unique index.

Solution: Run the repair process to fix the problem.

Index Clustered

In Microsoft SQL, index type can be classified as clustered or non-clustered. The verification process compares the required definitions for each index in the expected database user schema to the project database user schema.

Problem: If the verification process finds differences in the index clustered attribute definition, it generates an Index Clustered warning.

Solution: Run the repair process to fix the problem.

Missing Constraint

Constraints are rules that the database enforces to improve data integrity.

Problem: If the verification process finds a constraint that should be defined as missing, it generates a Missing Constraint warning.

Solution: Run the repair process to fix the problem.

Missing Index

The verification process checks that all the required indexes (as defined in the expected database user schema) exist in the projects database user schema.

Problem: If the verification process does not find all the required indexes in the projects database user schema, it generates a Missing Index warning.

Solution: Run the repair process to fix the problem.

Index Changed

The verification process checks that the indexes are defined according to the expected database user schema.

Problem: If the verification process finds an index that is not defined according to the expected database user schema, it generates an Index Changed warning.

This warning can indicate the following problems:

• Function in a function-based index is different than expected.

• Index is not defined on the expected columns.

Solution: Run the repair process to fix the problem. The repair process removes the index, and then recreates it, based on the required definitions for this index.

Index Order Changed

The verification process checks that the order of the columns in the index definition has not changed.

Problem: If the order of the columns in the index definition has changed, the verification process generates an Index Order Changed warning.

Solution: Run the repair process to fix the problem. The repair process removes the index, and then recreates it, based on the required definitions for this index.