Progress database updating

S

Steve Kuchta

New Member
Hi,

We are running Progress91D with Vantage 6.5. We currently have our "live" database and one we intend to use for manpower/machine forecasting. What I want to do is dump our "live" database into the forecasting database and run reports to see if we have enough capacity to take on various projects. After we start inputting projected data, how will I be able to "update" the forecasting database with the new data we run in the meantime?

Thank you,

Steve Kuchta
 
just regulary restore a backup?
If you only want to report then i think the only option to do this on alive and running database is with OE replication plus.

Casper.
 
What is OE replication plus? The idea my boss has is to have two databases, one for live use and one for forecasting purposes. He also likes the idea to have a working version of our database for fallback in case of failure of our live database. What I am hoping for is a way to do this via incremental backup. But I am not sure what probkup will do when it hits the forecasted data in the other database.

Thank you,

Steve Kuchta
 
There are several techniques for maintaining a warm spare, i.e., a reasonably current copy of the production database, but none of these techniques will work if you are modifying the second database. To do that, you are going to have to do something much more selective and have very careful rules. You might want to look at Tom Bascom's technique for direct database to database replication, modified for selective attention to the tables you need to update.
 
Replication plus is a Progress product that basically keeps a second copy of the db up and running and available for read-only reporting in real-time.

The second database can be on a different server.

The product is kind of expensive though. If you don't need real-time reporting then a restored backup is probably a better option.

You also need to be very sure that your reporting is read-only.

Restoring a backup (including an incremental) will overwrite the previous copy of the db. This probably isn't going to work for what you describe. Incremental backups are primarily a tool for reducing the amount of media needed to backup. IMHO they're basically useless.

There are many ways to create and maintain a warm spare. Some of them even support reporting. The devil, of course, is in the details.
 
I think the key question here is whether the work done on the "spare" is read-only. I get the impression it isn't, which makes all the difference in the world. If it is, then there are a bunch of choices.
 
You must log in or register to reply here.
Back
Top