| Best Practice for Batch Processing of Large Table [message #90641] |
Wed, 16 June 2004 09:02  |
Andy Ferretti
Messages: 1
Registered: June 2004
|
Junior Member |
|
|
I am wondering if anyone is aware of any best practices documented for design of a batch program that must step through a large table making updates to the large table as well as other dependent tables based on business criteria. We would want to allow for concurrent on-line transactions (so logging is necessary). We could commit at reasonable intervals (every 100 records or so). We would want to support restartability as well as the ability to run multiple threads simultaneously. Lastly, we would want to avoid problems with rollback segment space.
The programming environment here is java, however any best-practice in the form of a high level algorthm would suffice.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
