To Recap

We covered a lot of ground together in this chapter dealing with triggers and stored procedures. As you can see, trigger and stored procedure 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 and stored procedure 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.