Database Administration (MOSC)

MOSC Banner

Using materialized view to control access to database

edited Oct 23, 2018 5:04AM in Database Administration (MOSC) 4 commentsAnswered ✓

Hi All,

I've been asked by my management to find a way to limit a user's access to a certain table in our production DB. The catch is, they don't want that user's activity to disturb the running production DB server. Their concern is this user could issue a very complex select queries or issues too many select queries at a same time and will cause the DB server to run out of processes / sessions.

If it's just to limit user access, I have no problem creating a read-only user, but the management do not want this users to have any sort of impact to the production DB at all. The only thing in my mind is MViews, specifically my plan is to create a remote DB instance on another server, then sync the tables from the master production DB to it. This way the user can use the remote DB to query the same data as in production through MViews. I have yet to suggest to my management yet if they want the data

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center