Doug,
we generally take this approach when user need only restricted access.
An easy way to do so is to
1. make the owner of your application schema a group (if it is not
already) but don't grant rights on tables for that group,
2. create a read-only user,
3. make the user a member of the group and
4. grant the user select rights on all the needed tables/views/stps and
the like (which is likely to be only a part of your app's schema).
The "make the user a member of the group" part assures that the readonly
user can access tables without need to qualifying names. That might be
helpful if the user has to use existing queries where names are not
qualified.
I guess there are a bunch of topics in this (and the product futures) NG
according to your request.
HTH
Volker
Doug Stone wrote:
Quote:
One of our customers wants to have crystal reports access to our
application's database.
I think the best path is to setup a read-only user with access to all
our app's tables.
Does anyone have suggestions/cautions?
Thanks,
Doug |