Re: Jailing a schema from PUBLIC
- From: "Mark Brinsmead" <pythianbrinsmead@xxxxxxxxx>
- To: rjoralist@xxxxxxxxxxxxxxxxxxxxx
- Date: Sat, 17 Feb 2007 19:34:24 -0700
Crazy situations sometimes call for crazy solutions...
Create a separate database for Vendor "B". Create in this database a schema
that accesses Vendor "A" data through DBlinks. Add a second schema for
vendor "B"s use, that has only SELECT privilege on the views in the first
schema. It sucks, but at least the second database won't be affected by the
excessive privileges granted to PUBLIC... If you like, you can call this an
"Actual Private Database". :-)
After you're done all this, be sure to send the bill for all the work to
Vendor "A".
(If it works, the VPD idea sure sounds a lot better. But the APD approach
ought to work, too. Slowly.)
--
Cheers,
-- Mark Brinsmead
Senior DBA,
The Pythian Group
http://www.pythian.com/blogs
Other related posts:
