Looks good to me, except for step b.

You don't really need that.

I've used the same setup several
times successfully.

Jared


On Friday 06 July 2001 13:51, Thomas Jeff wrote:
> We came up with the below standards with respect to  database links
> (heavily
>
> used in our environment).   The result has been a billion complaints by
> our developers, stating that the standards are unnecessarily complex.  I'm
> curious as to what others might think, if they *are* indeed too complex.
> Also what kind of naming/adminstrative standards that other shops employ.
>
> 1. To access remote data across a DB LINK, the
>    standard implementation consists of four pieces:
>
> a) A private database link owned by the schema owner of the table
>    objects being accessed.  The CONNECT TO and IDENTIFIED BY clauses are
>    required
>    - Naming Standard:  {remote schema}_{database name}
>
> b) A standard PUBLIC SYNONYM created for the remote table being
>    accessed across the link.
>    - Naming Standard: {remote schema}_{remote table}.  The purpose of this
>      synonym is both to allow portability and also to provide documentation
>      of the remote connection.
>
> c) A VIEW created as a SELECT * from the PUBLIC SYNONYM above (1.b).
>    - Naming Standard: {remote table}_VW
>
> d) A PUBLIC SYNONYM on the VIEW above(1.c.)
>    - Naming Standard: {remote table}
>
> Thanks,
> Jeff T
> [EMAIL PROTECTED]

----------------------------------------
Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1"
Content-Transfer-Encoding: 7bit
Content-Description: 
----------------------------------------
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Jared Still
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to