If  we want to use after insert/update/delete triggers to log audit records into shadow tables, is there a way to find out if there will performance impact without developing the code?

The transactions are light volume in general. However we do have some transactions (once per month) that will insert 30,000 ROWS into a table. most other transactions are insert or update one ro few rows.

It sounds to me that we have to develop the trigger and run the transactionswithout auditing trigger and with trigger to see if there is any degredation in performance.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

slightwv (䄆 Netminder) Commented:
There will be overhead in doing this.  I'm not aware of any predictive forecasting tool that will predict how well unwritten code will perform.  

That is pretty much directly correlated to the efficiency of the written code.

I would set up a test system and run the with and without tests you mentioned.  Then you should be able to forecast future impacts.

Also, 30,000 rows isn't a lot of data.  Unless your system is really really stressed, I don't think you'll notice it but every system is different.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sam15Author Commented:
you would not have much code in after insert trigger.

just a simple insert of the ROW into audit shadow table. Think of 2 insert statements.
I might capture more fields like IP address, terminal id, userid, etc.

When you say there will be overhead do you mean like 0.1 seconds. this is not noticeable to me.

I was thinking of doing some tests in sql*plus. run a insert script or update or delete and see how long it takes with trigger enables and trigger disabled. do you think that would be valid tests or you have to use the application for more accuracy.

of course, in TEST there is always one user versus 50-100 users in producion but most transactions are single user by nature and the volume is low.
slightwv (䄆 Netminder) Commented:
From all your other questions on this topic I don't think you'll see much of a performance hit.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Analysis

From novice to tech pro — start learning today.