alternate for incremental backup

G

greenpower

New Member
Hi,

I have the following situation.
My Db is 35 GB and one of our department restores every night the full backup to a local system. From there they query 90% of the data tot a datawarehouse enviroment. This takes about 6 to 8 hours. This gives of course more and more time schedule problems.

Per day i only need the adds, deletes and changes of the data with i can add tot my DWH. I tried to load a incremental backup into en empty DB. But this doesn't work.

The only solution i am now aware of is making triggers on each table, but this is of course a lot of work and when we get a change from our software supplier my adds will be lost.

Can anybody help me with a nice solution.

Greetings,
Jan
 
You don't mention your version, but the most recent versions have auditing features which I would think you could use for this. There are also replication schemes which would keep you from having to do the backup and restore part, although they wouldn't give you the incremental changes for the data warehouse.
 
How about using after-imaging to keep a warm-spare database current?

So long as your data extracts are read-only (and it sounds like they would be) you could pause the roll forward processes and then use -RO sessions to extract the data.
 
Hi Tom,
As far as i can make out from ur statement, we can bring up the hot-spare DB with -RO and run queries. But my doubt is "if there are any in-flight transaction, can we restart the roll-forwarding again, from the point we left " .
 
As long as you only ever use -RO sessions against it you can continue to roll forward. The in flight transactions will be completed by the next roll forward just like they normally are.

It is not, however, advisable to run a -RO session while rolling forward. It won't hurt the roll forward process to do so but it might very seriously confuse the -RO session.
 
You must log in or register to reply here.
Back
Top