Using Dataguard for a cut down reporting database

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 Received on Wed Mar 19 2003 - 08:07:56 CST