Re: two instance -- one database

The reason I use a scenario like the one you describe is that the security concerns outweighed the negative impact to performance. I'm not sure how dblinks protect from bad queries...

In any case, we use JD Edwards Enterprise One. The first thing it does after creating a table in Oracle is "GRANT ALL ON schema.table TO PUBLIC;". Joy. An auditor's dream.

Instead of hacking with triggers and timing, I chose to not create any other schemas in our production JDE DB. Instead, we have an ancillary DB where the DML security is controlled via views over a dblink to the JDE DB. While more elegant (perhaps), it's not best for performance.

My $.02,
Rich

> I have a friend (no really, this isn't some lame way of telling you about me
> but trying to hide that by ... )
>
>
> I have a friend, and at his company they have an Oracle database with tables
> and data. We'll call it Database A and they have another Database B that has
> views across dblinks to each of the tables in Database A. The data team says
> that this protects Database A from bad queries.
>
> So can anyone think of any possible benefit from this arrangement? Will
> administration be easier, queries faster, performance more predictable?
> Anything?

--
http://www.freelists.org/webpage/oracle-l