RE: Avoid a synonym

It is not applicable in all situations but I have used a schema after_logon trigger which does an "alter session set current_schema=nnn" to avoid needing to create massive amounts of synonyms. Of course that only works if the user needs access to only objects in one schema. If you need to do that for very many users then a database after_logon trigger may be easier to manage.

Quoting DENNIS WILLIAMS <DWILLIAMS_at_LIFETOUCH.COM>:

> Nuno - Good point (as always). My reasons are as follows:
>
> 1. The application group has their strategy built around public synonyms.
> 2. My boss likes public synonyms.
> 3. As I recall, it was Jonathan Lewis who mentioned that public synonyms
> could cause performance problems, and I have passed that along to my boss.
> If anyone has a personal horror story to share, that might make an impact.
>

-- 
regards

Wolfgang Breitling
Oracle 7,8,8i,9i OCP DBA
Centrex Consulting Corporation
www.centrexcc.com

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