<img src="02start60.gif" height="25" width="100"> STOP VIOLATIONS TABLE

Informix Guide to SQL: Syntax
SQL Statements

STOP VIOLATIONS TABLE

Use the STOP VIOLATIONS TABLE statement to drop the association between a target table and the special violations and diagnostics tables.

In Enterprise Decision Server, the diagnostics table does not exist. The STOP VIOLATIONS TABLE statement drops the association between the target table and the violations table.

Syntax

Element Purpose Restrictions Syntax

table Name of the target table whose association with the violations and diagnostics table is to be dropped No default value exists. The target table must have a violations and diagnostics table associated with it before you can execute the statement. The target table must be a local table. Database Object Name, p. 4-50

Element	Purpose	Restrictions	Syntax
table	Name of the target table whose association with the violations and diagnostics table is to be dropped No default value exists.	The target table must have a violations and diagnostics table associated with it before you can execute the statement. The target table must be a local table.	Database Object Name, p. 4-50

Usage

The STOP VIOLATIONS TABLE statement drops the association between the target table and the violations and diagnostics tables. After you issue this statement, the former violations and diagnostics tables continue to exist, but they no longer function as violations and diagnostics tables for the target table. They now have the status of regular database tables instead of violations and diagnostics tables for the target table. You must issue the DROP TABLE statement to drop these two tables explicitly.

When Insert, Delete, and Update operations cause data-integrity violations for rows of the target table, the nonconforming rows are no longer filtered to the former violations table, and diagnostics information about the data-integrity violations is not placed in the former diagnostics table.

Example of Stopping a Violations and Diagnostics Table

Assume that a target table named cust_subset has an associated violations table named cust_subset_vio and an associated diagnostics table named cust_subset_dia. To drop the association between the target table and the violations and diagnostics tables, enter the following statement:

STOP VIOLATIONS TABLE FOR cust_subset

Example of Dropping a Violations and Diagnostics Table

After you execute the STOP VIOLATIONS TABLE statement in the preceding example, the cust_subset_vio and cust_subset_dia tables continue to exist, but they are no longer associated with the cust_subset table. Instead they now have the status of regular database tables. To drop these two tables, enter the following statements:

DROP TABLE cust_subset_vio;
DROP TABLE cust_subset_dia;

Privileges Required for Stopping a Violations Table

To stop a violations and diagnostics table for a target table, you must meet one of the following requirements:

You must have the DBA privilege on the database.

You must be the owner of the target table and have the Resource privilege on the database.

You must have the Alter privilege on the target table and the Resource privilege on the database.

Related Information

Related statements: SET Database Object Mode and START VIOLATIONS TABLE

For a discussion of database object modes and violation detection, see the Informix Guide to SQL: Tutorial.