Re: When and when not to create SP/triggers

Thomas J. Girsch wrote: > <snip> > there should be at most one SP called. > <snip> Hi-Thomas, I won't agree with that "at most one SP for every trigger", when you implement business rules using triggers & SPs, you could avoid duplication of common logic by designing/coding them into SPs with modularized common logic. These common business logic can be enforced in triggers and programs by executing those SPs. You can call one junk-SP with all values which eventually calls required SPs, which I won't recommend, so why not call individual SPs as you need them ? -- Have a nice day Felix K. Mathews mailto:fmathews@systems.dhl.com