To Recap

We covered a lot of ground together in this chapter dealing with triggers. As you can see, trigger writing and management can consume substantial resources, and without proper planning, documentation, change control, archiving, source code maintenance, modeling, and so on, you can create a lot of problems for yourself or the team.

If you are new to trigger writing, the change in development style and philosophy can put a lot of strain on mental and physical resources. And the conversion of client-side, inline SQL code to server-side triggers (and stored procedures) can be expensive in terms of both time and materials.

If you have not already done so, you should read Chapter 6 carefully, or read it again, because trigger and stored procedure deployment require you to manage permissions and security so that your users can exploit the code you have written. Also, query plans are discussed in Chapter 16, and understanding them is an essential prerequisite to writing and testing stored procedures and triggers.