Re: Snapshot of Data on a seperate database

I am not sure whether materialized views is the solution.

Is that what replication uses. What about read only replication where the external database gets refreshed every n minutes. It should be easier than advanced Multimaster replication.

Please suggest.

Thanks
Ron

"Gerry Sinkiewicz" <sinkiege_at_snet.net> wrote in message news:<A10Nb.56607$5c7.16369_at_newssvr31.news.prodigy.com>...
> "Ronnie" <ronnie_yours_at_yahoo.com> wrote in message
> news:ea603f8d.0401121524.1518ea13_at_posting.google.com...
> > Hi,
> >
> > We have 2 databases one internal OLTP database and another external
> > which our clients access.
> >
> > We want to have a snapshot of the internal database on our external
> > database so that our clients can have read only access to the external
> > database.
> >
> > I came up with the following solutions
> >
> > Export the whole schema and import it into the external database. But
> > this has turned out to be a pain as I will have to drop the schema and
> > recreate it and then import the tables.
> >
> > Implement views on the external database for each and every table in
> > the internal database, but this will increase the load on our internal
> > database and more important since our internal database is licensed on
> > Named user plus, every client of ours that connect to our database
> > will be a Named User. (Our external database is licensed on number of
> > processors but since views will access the internal database through
> > database links oracle treats these as Users)
> >
> > Is there any other better solution to do this.
> >
> > Maybe Replication....
> >
> > Please suggest.
> >
> > Thanks
> > Ron
>
> Snapshot, yes replication.
> Things called materialized views, used to be called snapshots (see create
> snapshot).
> This does not even need advanced replication it is part of basic Oracle EE.
> It will solve the licensing issue.
>
> The only other solution would be to place the internal database on the
> outside (not recommended)
> on the same CPU licensed server, or bring the external DB inside and use
> and app (IIS) in a DMZ to access
> the data through a pinhole in the firewall or sql-proxy.
Received on Wed Jan 14 2004 - 13:31:34 CST