Q16
True / FalseThe CHECK constraint allows you to limit the range of values for a column.
The CHECK constraint is used to enforce domain integrity by restricting the values that can be placed in a column.
Q17
True / FalseA CHECK constraint can be applied to multiple columns in a table.
CHECK constraints can be defined to apply to multiple columns, with conditions involving those columns.
Q18
True / FalseThe CHECK constraint can be used to enforce referential integrity.
Referential integrity is enforced using foreign keys, not CHECK constraints.
Q19
True / FalseCHECK constraints can be used to ensure that a column value is within a certain range.
CHECK constraints are often used to enforce that a column's value falls within a specific range or meets certain criteria.
Q20
True / FalseA CHECK constraint can be defined to allow NULL values in a column.
CHECK constraints apply to non-NULL values, but if a column allows NULLs, the constraint does not apply to NULL values.
Q21
True / FalseA CHECK constraint can be used to limit the number of rows in a table.
CHECK constraints apply to individual column values, not the number of rows in a table.
Q22
True / FalseThe CHECK constraint can enforce business rules within a database.
CHECK constraints are useful for enforcing business rules on the data stored in the database.
Q23
True / FalseYou can apply a CHECK constraint to a computed column.
CHECK constraints can be applied to computed columns to ensure the computed results meet certain criteria.
Q24
True / FalseA CHECK constraint can include a condition that involves other columns in the table.
CHECK constraints can use expressions involving multiple columns to enforce complex rules.
Q25
True / FalseThe CHECK constraint is automatically indexed to improve performance.
CHECK constraints do not automatically create indexes; performance improvements are achieved through other indexing strategies.
Q26
True / FalseYou cannot drop a CHECK constraint once it has been created.
CHECK constraints can be dropped or modified using SQL commands like ALTER TABLE.
Q27
True / FalseCHECK constraints can be disabled and re-enabled later.
SQL Server allows CHECK constraints to be disabled and re-enabled as needed.
Q28
True / FalseThe CHECK constraint can be used to validate the data being inserted into a column.
CHECK constraints validate data against specified conditions when it is inserted or updated in a table.
Q29
True / FalseA CHECK constraint can include a subquery to enforce column value constraints.
CHECK constraints do not support subqueries; they only allow simple expressions for validation.
Q30
True / FalseThe CHECK constraint can be applied to a table or an individual column.
CHECK constraints are typically applied to individual columns, but they can enforce rules involving multiple columns as well.