Tag: check constraint

Pro Members SQL Server Standard Members

Tips for using SQL Server 2017 triggers

by

Tips for using SQL Server 2017 triggers Try to use CHECK constraints instead of triggers whenever possible. Constraints are much more efficient than triggers and can boost performance. Constraints are also more consistent and reliable in comparison with triggers, because you can make errors when you write your own code to perform the same actions as the constraints. So, you...

This content is for Pro, Pro Member, Pro Member Annual - Fall Sale, Pro Member Monthly - Fall Sale, Standard, Standard Member, Standard Member Annual - Fall Sale, and Standard Member Monthly - Fall Sale members only.
Register
Already a member? Log in here
Continue Reading →
Pro Members SQL Server Standard Members

Tips for using constraints in SQL Server 2017

by

Tips for using constraints in SQL Server 2017 Use cascading referential integrity constraints instead of triggers whenever possible. For example, if you need to make cascading deletes or updates, specify the ON DELETE or ON UPDATE clause in the REFERENCES clause of the CREATE TABLE or ALTER TABLE statement. The cascading referential integrity constraints are much more efficient than triggers...

This content is for Pro, Pro Member, Pro Member Annual - Fall Sale, Pro Member Monthly - Fall Sale, Standard, Standard Member, Standard Member Annual - Fall Sale, and Standard Member Monthly - Fall Sale members only.
Register
Already a member? Log in here
Continue Reading →
SQL Server

Tips for using constraints in SQL Server 2016

by

Tips for using constraints in SQL Server 2016 Try to create a single column constraint. The more columns the constraint will have, the slowly it will work and the more stored space it will require. Use default constraints instead of DEFAULT objects. DEFAULT object are provided for backward compatibility and has been replaced by default definitions (default constraints) created using […]

Continue Reading →
Pro Members SQL Server Standard Members

Tips for using SQL Server 2012 constraints

by

Tips for using SQL Server 2012 constraints Try to create a single column constraint. The more columns the constraint will have, the slowly it will work and the more stored space it will require. Use cascading referential integrity constraints instead of triggers whenever possible. For example, if you need to make cascading deletes or updates, specify the ON DELETE or...

This content is for Pro, Pro Member, Pro Member Annual - Fall Sale, Pro Member Monthly - Fall Sale, Standard, Standard Member, Standard Member Annual - Fall Sale, and Standard Member Monthly - Fall Sale members only.
Register
Already a member? Log in here
Continue Reading →