Using a Trigger to partition your processing

During a large invoicing run, updates are made to an invoicing table within a Pro*C program; however, the invoicing table has an insert trigger on it which causes updates to be made to a separate table. This program takes several hours to execute, so we are looking at ways to optimize it.

My question is: is there an advantage to 'encapsulating' some of the update processing (to the second table) within the trigger as described above, or are there inefficiencies or drawbacks to doing it this way? The updates to the 2nd table could have just as easily been written into the Pro*C module in the appropriate place.

Thanks,

Geoff Houck
systems hk
hksys_at_teleport.com
http://www.teleport.com/~hksys Received on Tue Feb 13 2001 - 01:24:27 CST