DB2 triggers to send realtime data

rz061m · New User Joined: 03 Mar 2006 Posts: 48 Location: Chennai

Hi all,

I need suggestion on the solution proposed for one of our customers requirement. We are yet to begin the development activities, so trying it out in real environment region is not feasible at this time.

Customer wants a set of data (from 3 different tables) to be sent every time a row is inserted or updated in a particular table. I could use a DB2 trigger to achieve this but wanted to know :

1. How it would perform when there is a real time situation of more than 10,000 data updated in less than a minute.

2. Will the trigger send data one after the other when some other rows are parallely updated

3. Our MIPS consumption is close to 80%, will these triggers eat up more MIPS and cause performance issue for UI applications

4. Some of the application program performs COMMIT only at the end of the program and some programs perform COMMIT after specific count of records. How these trigger behave if programs abends in the above said 2 scenarios.

Rohit Umarjikar · Posted: Fri Jul 17, 2015 8:20 pm

Better use DB2 SP or DB2/MQ SP.

Pandora-Box · Posted: Sat Jul 18, 2015 2:26 am

166 triggers per second I feel its bombarding the system

Also suggest to talk to your DBAs first as this could turn out as a bigger problem

And also having triggers might degrade the performance of the process / program (Considering the fact of 10,000 updates less than a minute ) that is updating the table