Re: Back to the future

Dear Dino,
I feel having a standby database is a better solution for that. I used to maintain a 1TB database which have a standby database. Exporting the database
was out of question as the window was very small. The log switches occour
by half an hour frequency. There are a few instances when users dropped tables and came to me. In most cases my activity was to open the standby database readonly, export the needed table and import it back to production.
Takes less pain. But the resources...

Thanks
Saikat

"Dino Hsu" <dino1.nospam_at_ms1.hinet.net> wrote in message news:b06cpt4kd56jtgcehupqguumo2d436r4s9_at_4ax.com...

> Dear all,
>
> I've just studied the backup and recovery part, and I learned about
> the incomplete recovery and realize that the database can roll forward
> from a baseline backup using log files, this is like 'going back to
> the future'. We can issue 'recover database until canel' to roll
> forward to a point in time. However, without 'WYSWYG' and 'rewind'
> functions, I would assume it's difficult to reach the exact point in
> time. For example, your user tells you he inadvertently dropped a
> table at around 10:00, but nobody knows the exact time, when you
> recover to the 10:00 point, you cannot see the data on the run because
> the database is not opened yet. If the actual time is 09:50, and you
> open the database at the 10:00 point (resetlog), only to see the table
> is still missing, you can do nothing except to start over again. This
> is just like when the police is investigating on a robery case, they
> check the video tape trying to get to the point in time, with 'WYSWYG'
> and forward/backward functions, it's quite easy. But without 'WYSWYG'
> and backward functions, it's time-consuming to narrow the way down
> there.
>
> I am bothered by this thought, anyone enlightens me? Thanks in
> advance.
>
> Dino

-- 
Posted from  [203.197.125.228] 
via Mailgate.ORG Server - http://www.Mailgate.ORG