>>-STOP VIOLATIONS TABLE FOR--table----------------------------><
| Element | Description | Restrictions | Syntax |
|---|---|---|---|
| table | Name of a target table whose association with the violations and diagnostics table is to be dropped. No default value exists. | Must be a local table that has an associated violations table and (for IDS) a diagnostics table | Database Object Name, p. Database Object Name |
The STOP VIOLATIONS TABLE statement drops the association between the target table and the violations table (and for Dynamic Server, the diagnostics table). 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 DML operations (INSERT, DELETE, or UPDATE) cause data-integrity violations for rows of the target table, the nonconforming rows are no longer filtered to the former violations table, and diagnostic information about the data-integrity violations is not placed in the former diagnostics table.
In Extended Parallel Server, the diagnostics table does not exist. The STOP VIOLATIONS TABLE statement drops the association between the target table and the violations table.
Enterprise Edition Home | Express Edition Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]