rmespas80 wrote:Yes, of course. Anything you do in the database affects its performance.
I want to perform an analysis of a database, but I have some questions about things that are more desirable or not. for this I would like to make some questions and see if I can help to clarify my doubts:
Problems that have to use cursors in triggers.
Affects the performance of the database?
To what extent is advisable to use triggers?Use triggers as little as possible.
rmespas80 wrote:That's a lot of triggers! Do you really need all of them?
this was my question, since in several tables have something like the following:
12 triggers for table
• BIR Before Insert RowOracle provides some built-in auditing, which is more reliable than, and almost certain to be more efficient than, any user-defined triggers to do the same thing.
• BDR Before Delete Row
• BUR Before Update Row
• BIS Before Insert Statement
• AIR After Insert Row
• AIS After Insert Statement
• BUS Before Update Statement
• AUR After Update Row
• AUS After Update Statement
• BDS Before Delete Statement
• ADR After Delete Row
• ADS After Delete Statement
triggers execute in various validations, calling packages and other queries.
above the triggers were created with an application to manage business rules and audit, all the logic is in the database.
This application was who default towards creating triggers are used or not.Sorry, I don't understand this last sentence at all.
I need to demonstrate that the triggers affect the development and performance of a Web applicationWhat do you mean by "affect the development"?