You've got a piece of code that you want to implement as a trigger, but you've read that triggers can grind your performance to a halt. Developers everywhere write triggers to implement business logic, to enforce certain types of constraints, or to avoid changing database schema or external code. Many triggers are inefficient and violate best practices, but it doesn't have to be this way. Join this session and learn how to improve your triggers and keep them off the list of potential scapegoats for your SQL Server performance woes.
Presented by Aaron Bertrand at SQLBits XIV
MP4 Video HD 439 MB