Trigger impact on overall DB performance
Posted on 2001-07-26
We currently have a Vitria Enterprise Application Integration implementation in progress. One of the systems we're integrating is a billing system. The client is extremely concerned with the performance impact on the billing system, due to some current application performance issues.
What we're doing to the billing system's Oracle database is the following:
- The DB currently has MANY triggers on different tables
- We will be creating one (1) extra table for Vitria
- We will be adding a trigger on an existing table to write to the new table -> the trigger will be inserting 15~20 fields of data (from 1 table) to the new table (no complex SQL at all)
- During each billing cycle, the # of record sets being processed is around 110,000 - we'll be capturing the change only in one table (so around additional 110,000 trigger fires and table inserts)
We've been promised by Vitria (the vendor) that this would pose zero or minimal impact to the Oracle DB. We've also heard from a similar project that the impact to the system is not noticeable. However, the client is still extremely concerned.
What we'd like to know is -> what type of impact can we expect by adding this relatively simple trigger to the database?
Please provide as much detail (if there're any) as possible. Thanks very much in advance!