Re: Using Dataguard for a cut down reporting database

Paul wrote:
>
> I have been reading about DataGuard and its use for creating one or
> more standby databases.
>
> Is it possible to use the same features to create a reporting
> database, but limit the tables (or data within a table) that is
> maintained in the standby.
>
> For example if the primary database has a particularly large table
> with lots of activity (inserts, updates), but the reporting database
> doesn't need to see all this data, can it be configured to ignore or
> skip the elements of the shipped log files that relate to this table?
>
> Being able to do so would save time in applying the logs, but more
> importantly allow for a much smaller reporting database.
>
> Thanks
> Paul

The "logical" standby option in Dataguard scrapes the redo logs to find the originating SQL to apply to another database, thus allowing that other database to drift out of synch with the source.

I haven't played with whether you can use subsets of the source database.

hth
connor

-- 
=========================
Connor McDonald
http://www.oracledba.co.uk

"Some days you're the pigeon, some days you're the statue"