Re: Security, private vs. public synonyms and contention data di

[Tanel Poder]

Title: RE: Security, private vs. public synonyms and contention data dictionary

A lot of people have posted messages like: "I have several applications in my DB, but I can't create new public synonyms for my new app, because public synonym with that name already exists!". So, this should be one major reason why not to use public synonyms,   But yes, check ixora, there is a very good explanation about impact of synonyms. Generally, public synonums are worst performance wise, private synonyms aren't that good either, referencing to tables directly in your SQL would be the fastest way (talking about parsing speed). Since from developers point of view hardcoding the schema names would be quite bad, there's an alternate solution of not hardcoding schema names to SQL, but using alter session set currecnt_schema in your application to set which schema should be used (of course in multi-schema environments you won't get away with that easily).   Tanel.   ----- Original Message ----- From: Stephane Paquette To: Multiple recipients of list ORACLE-L Sent: Friday, July 11, 2003 10:49 PM Subject: RE: Security, private vs. public synonyms and contention data di I think I remember Steve Adams posting something about performance and public synonyms, you may want to check its web site www.ixora.com.au   Stephane Paquette Administrateur de bases de donnees Database Administrator Standard Life www.standardlife.ca Tel. (514) 499-7999 7470 and (514) 925-7187 [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of [EMAIL PROTECTED] Sent: Friday, July 11, 2003 3:35 PM To: Multiple recipients of list ORACLE-L Subject: RE: Security, private vs. public synonyms and contention data di Question: Are private versus public synonyms preferred for security? Are private syn. worse administration? Do 1,000 users with private syn. cause data dictionary contention?