Violation Reports

USoft BenchMark enables you to create violation reports. Three reports can be created:

·	Constraint violation report

This is a report on constraints that have been violated. This may be useful when new constraints have been introduced, when you have doubts about the database integrity, or when data has been loaded or manipulated.

It is possible to report on a selection of constraints by excluding the ones that you do not want reported.

Transitional constraints, constraints containing an INVOKE statement, constraints without a FROM clause in the main query, and constraints that are deferred until post-commit are NOT reported..

A list of primary keys of the records violating the constraints is included in the report.

Note that if a corrective constraint violates, you can work around the violations by running the SQL of the constraint in the SQL command utility in the application. You should take care with this approach, and violations should always be investigated: it could be the case that running the constraint SQL is not the required solution, and other values may have to be updated. Furthermore, bear in mind that running the constraint SQL to work around the violation may trigger other constraints.

·	Relationship violation report

USoft Developer checks records when they are manipulated. In some situations, such as a change of the data model, or when the application tables have been changed by means of a non-USoft tool, it is necessary to check the contents of the application tables against the rules defined in the repository.

This report contains all violations on attributes of relationships. This includes the cases where:

·	A child record misses mandatory parent.

·	A child record has non-existing parent.

·	A parent record is missing mandatory children.

·	A parent record has too few or too many children.

For each relationship, the report includes the primary keys of all records that violate one of the rules and the type of violation. It also includes total number of violations per table and relationship.

It is possible to report on a selection of relationships by excluding the ones that you do not want reported.

·	Column violation report

This is a report on column values that have been violated. This may be useful when column and domain attributes have been changed, when you have doubts about the database integrity, or when data has been loaded or manipulated. You can report on one or more of the following aspects:

Uppercase

·	Fixed Length

·	Minimum Value

·	Maximum Value

·	Allowed Values

·	Domain Constraints

Mandatory

·	Uniqueness

It is possible to report on columns of a specific table only, and on columns based on a specific domain.

NOTE:

No reporting is provided for the following:

Subtypes

·	Subtype rules (exclusive, total)