Is any problem if table has more triggers

**nilopher** · 01-03-2003, 04:10 AM

Hi All,

Is any difficulty get occurred if a table has
more triggers (5 or so).

Thanks.

**SANJAY_G** · 01-03-2003, 04:56 AM

It depends on what the triggers do. If it takes long to process the trigger code the performance of the triggering event (insert, update, delete) and the overall performance of the database may degrade. Otherwise I don't see any problem.

HTH

**nilopher** · 01-03-2003, 05:23 AM

All the trigger codes contains a simple logic like
selecting some values updating the values in all
events (inserting, updating, deleting).

Thanks Sanjay.

**vastdba** · 01-03-2003, 06:07 AM

The Triggers which is at back end will only fire on its event occuring. However, It weighs the database from its space allocation and subsequently overhead problems occur when properly not utilised.
Such as
Application overload;
If it is recursive then creates other triggers to fire on its invocation;
Back-End consumation;
DML operations in particular causes mutating the table.

VAST

**virajvk** · 01-03-2003, 06:17 AM

Total time would be proportional to the sum of time taken by individual statments.

When you say u r updating table u may update large table that can time.

Various other factors can also cause delay in executing all triggers.

Can you minimize your buisness logic ? May be some part of it you can code in Application itself.

Regards
viraj
--------
9i OCA

**Sameer** · 01-03-2003, 07:16 AM

Originally posted by virajvk

Can you minimize your buisness logic ? May be some part of it you can code in Application itself.

This is not advisable. Performing database related stuff are always better on backend than coding it in application.

Sameer

**vastdba** · 01-03-2003, 07:22 AM

Originally posted by Sameer
This is not advisable. Performing database related stuff are always better on backend than coding it in application.

Sameer

I fully agree with SAMEER as it coincides with the concept of minimizing the code length and application build length. The Beauty of triggers is it only fires on the event occuring.

Anyhow Business logic cannot be minimized, since client is the best end-user for which all these applications were framed.

Good discussion ..........Keep it up ALL.

VAST

**virajvk** · 01-03-2003, 08:21 AM

I agree Buisnes Logic coming from client can not be minimize but DBA can always think of Optimzing the operations by considering varous options
E.g. You can use more Materialized Views.

Analyzing true & optimized requirement of triggers is my stragey of working.

Regards

Viraj
********
9i OCA

**julian** · 01-03-2003, 12:13 PM

As far as I remember there is one limitation about triggers (even in 9i):

The Trigger Cascade Limit is 32.

**tamilselvan** · 01-03-2003, 03:42 PM

Definitely triggers on table are performance bottleneck. Try to avoid them.
The same business logics (functions) can be achieved in procedures and views.

Thread: Is any problem if table has more triggers

Thread Tools

Display