Such constraints are typically enforced by VectorH generating secondary indexes, and these in turn may degrade performance. However, VectorH also provides a mechanism whereby such constraints can be declared as NOT ENFORCED. This type of constraint can often help third-party tools generate “better” SQL and in turn provide better query execution. As the name implies, however, such constraints are not enforced, meaning that the actual data may not conform to the constraint.