Practice Questions: Constraints and Integrity

The syntax you would use is
ALTER TABLE WITH NOCHECK
ADD CONSTRAINT pk_name
ON

The syntax you would use is
ALTER TABLE
ADD CONSTRAINT pk_name
NOCHECK
ON

You can't add a primary-key constraint to a table with existing data.

You can add the constraint, but you can't turn off the check of the existing data.

Place a check constraint on the column to make sure the value entered is IN (table listing part numbers).

Place a check constraint on the column to make sure that the value entered is IN (SELECT part_no FROM parts_list) where parts_list is a table listing the part numbers and descriptions.

Build a foreign-key reference from this column to the part_no column in the parts_list table, where parts_list is a table listing the part umbers and descriptions.

Build a foreign-key reference to this column from the part_no column in the parts_list table, where parts_list is a table listing the part numbers and descriptions.

You can't drop and rebuild the index because the constraint automatically builds it; therefore, you can't change the fill factor.

You can drop and recreate the constraint, which lets you specify a fill factor for the index.

You can rebuild the index using the DROP EXISTING option and specify the correct fill factor.

You can't apply a fill factor to indexes built automatically by constraints.

When you try to delete a record, the constraint activates first, followed by the trigger.

When you try to delete a record, the constraint activates but the trigger doesn't.

When you try to delete a record, the trigger overrides the constraint.

You can't have both a trigger and a constraint enforcing the same referential integrity.