|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Updating records in DB |
« View previous topic :: View next topic » |
Author |
Message
|
MasterMind |
Posted: Sun Jul 24, 2011 10:03 am Post subject: Updating records in DB |
|
|
Newbie
Joined: 09 Nov 2010 Posts: 9
|
Folks,
Just want to check if ne one has tried this before successfully.
I want to check my local database on a daily basis at the end of the day and do the following activities...
1. extract all the orders existing in the database
2. run each of them through a list of validations which needs me to query different other databases for each order to get required information for validation.
3. after validation the status of the order needs to be updated in the database accordingly.
environment AIX
implementation using MB 7
DBs involved Oracle, SQL server , DB2
record size - 2 KB.
Load - to batch process more than 300K records. Do you think if we can come out with a scalable solution to handle increased load in future.
Regards,
RS. |
|
Back to top |
|
 |
Vitor |
Posted: Sun Jul 24, 2011 11:56 am Post subject: Re: Updating records in DB |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
MasterMind wrote: |
Just want to check if ne one has tried this before successfully. |
Yes.
There are a number of ways to achieve this, most of which will scale very well.
I'd propagate each of the results in a separate message to be validiated & used in an update. This allows the full range of WMB/WMQ load balancing & scaling techniques.
Other, possibly better, solutions are undoubtably available _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
MasterMind |
Posted: Sun Jul 24, 2011 12:38 pm Post subject: |
|
|
Newbie
Joined: 09 Nov 2010 Posts: 9
|
So ne limitations on the number of records , 300,000 to 500,000 records per batch ? |
|
Back to top |
|
 |
WGerstma |
Posted: Mon Jul 25, 2011 1:09 am Post subject: |
|
|
Acolyte
Joined: 18 Jul 2011 Posts: 55
|
As said:
Build one flow triggered by cron to select and propagate your orders. Tahn build seperate flows for validation, and use standard WMB/MQ load balancing features. You should not get problems with scaleability, but sure you have to compute adequate hardware sizing. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|