Thomas wrote:
> Our production database grows way too big for online reporting.
>
> The idea is to have a standby database on a different machine. This
> standby database *must* be cumulative in nature. It must contain all
> the data that ever existed in the prodution database -- when older
> records in the production database are deleted, they should not be
> deleted in the standby.
>
> Questions:
> 1) Is Dataguard the best way to have a standby with Oracle 9i? If
> not, what do you suggest?
>
> 2) can Dataguard be configured to propagate only updates and inserts,
> but not deletes?
You call it a "standby database" but you want it to act as an archive DB.
You really need to decide which it will be. Otherwise, you are going to have a
maintenance nightmare no matter what tool you use to populate the second DB.
--
Ed Prochak
running: http://www.faqs.org/faqs/running-faq/
family: http://web.magicinterface.com/~collins
--
"Two roads diverged in a wood and I
I took the one less travelled by
and that has made all the difference."
robert frost
Received on Fri Feb 21 2003 - 11:48:52 CST
