Re: Corporate Wide Public Synonyms

From: Richard Foote <richard.foote_at_bigpond.nospam.com>
Date: Fri, 11 Feb 2005 07:19:04 GMT
Message-ID: <I%YOd.155917$K7.78680@news-server.bigpond.net.au>

<linuxgeek_00_at_yahoo.com> wrote in message news:1108068838.968042.219230_at_f14g2000cwb.googlegroups.com...
> My company wants to implement a corportate wide public synonym model
> for our oracle 9i database. Meaning that every table in every schema
> would have a public synonym created against it. Personally I think
> this is a bad idea. However I need to develop a convincing arguement
> to change this policy that has been suggested by our "DBA's".
>
> One issue is that I'm aware of is that all table names must be unique
> across all schemas. Please let me know other reasons why it is a bad
> idea to create public synonyms for every table in every schema.
>

At a site I work, they previously had a couple of thousand or so users accessing everything through public synonyms. Latch contention was a significant performance bottleneck.

By using setting the appropriate current_schema via a logon trigger, the associated latch contention issues pretty well vanished.

Avoid public synonyms if practical.

Cheers

Richard Received on Fri Feb 11 2005 - 01:19:04 CST