Need advices about a development solution

Billy Larsen

Need advices about a development solution
Dear all,
Please , tell me what do you think about this :

Problem : Each updates on table A generates an "ask for update" on the
total value on table B. For table B , only the last update requested is
necessary. As B is only processed in a night batch.
All updates in table A are recorded in an MQ series queue.
Volume estimates : 200.000 ask for updates whereas 200 are really necessary

Solution 1 : all "ask for updates" are processed => 200.000 updates
Solution 2 : These "ask for updates" are stored in DB2 , and at the end of
the day, the latest ask for updates is processed => 200.000 inserts + 200
updates
Solution 3 : Unload the MQSeries Queue, sort to take only the latest
timestamp records, and updates these select records => 200 updates

Solution3 is obviously more interesting for DB2 , please tell me what do
you think ?

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

jwkwan2000

Re: Need advices about a development solution
(in response to Billy Larsen)
Solution 3 does seem the best if you only consider the db2 overhead.
However you need to also consider the operation and administration issues.
You might want to ask questions such as it is easy to upload MQSeries Queue?
How about error handling if it failed to upload? How easy is it to make
program modification in future?

200,000 inserts in solution 2 might seem a lot, but if it is spread out to
200,000 transactions, then the addition overhead to each transaction not be
significant. The advantage of using solution 2 is it is simple. You only
need a single program to do the job and it is relative easy to make changes.

The other possible solution which is not in your list is to extract updates
from DB2 log and make update to your B table.

I hope this will help you to make a better decision.

James Kwan

----- Original Message -----
From: "Billy Larsen" <[login to unmask email]>
Newsgroups: bit.listserv.db2-l
To: <[login to unmask email]>
Sent: Friday, January 07, 2005 4:51 AM
Subject: [DB2-L] Need advices about a development solution


> Dear all,
> Please , tell me what do you think about this :
>
> Problem : Each updates on table A generates an "ask for update" on the
> total value on table B. For table B , only the last update requested is
> necessary. As B is only processed in a night batch.
> All updates in table A are recorded in an MQ series queue.
> Volume estimates : 200.000 ask for updates whereas 200 are really
> necessary
>
> Solution 1 : all "ask for updates" are processed => 200.000 updates
> Solution 2 : These "ask for updates" are stored in DB2 , and at the end of
> the day, the latest ask for updates is processed => 200.000 inserts + 200
> updates
> Solution 3 : Unload the MQSeries Queue, sort to take only the latest
> timestamp records, and updates these select records => 200 updates
>
> Solution3 is obviously more interesting for DB2 , please tell me what do
> you think ?
>
> ---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
> home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
> select "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. The IDUG List Admins can be reached at
> [login to unmask email] Find out the latest on IDUG conferences
> at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm