SQL Server Tutorial : How DML triggers are used

Want to learn more? Take the full course at https://learn.datacamp.com/courses/building-and-optimizing-triggers-in-sql-server at your own pace. More than a video, you'll learn hands-on coding & quickly apply skills to your daily work. --- Now that you have a basic understanding of what triggers are, let's find out more about the reasons for using them. Developers and database administrators can create and use triggers for a multitude of purposes. The main reason for using triggers is to initiate actions when manipulating data (inserting, modifying, or deleting information). Sometimes the manipulation of data needs to be prevented, and this can also be done with the use of triggers. Another use case often seen in practice is using triggers for tracking data changes and even database object changes. Database admins also use triggers to track user actions and to secure the database by protecting it from unwanted changes. As mentioned earlier, it's important to understand the difference between the AFTER and INSTEAD OF trigger types so you know when to use each. From a trigger definition perspective, the two types of triggers look almost the same. But in practice, they will have very different outcomes when fired. The outcome of the trigger execution is highly dependent on the keyword you choose (AFTER or INSTEAD OF). The AFTER trigger adds new statements to the initial one, while the INSTEAD OF trigger prevents the initial statement from executing. This difference will influence the use cases for each type of trigger. One example of using an AFTER trigger is for a large insert of data into a sales table. Once that data gets inserted, a cleansing step should run to remove or repair any unwanted information. The cleansing step will be started by the trigger. When the cleansing step finishes, a report with the results will be generated. This report should be analyzed by a database administrator, so the trigger will then send an email to the responsible peopl