Return-Path: <root@fatcity.cts.com>
Received: from ensim.rackshack.net (root@localhost)
 by orafaq.net (8.11.6/8.11.6) with ESMTP id h1ELwtK06646
 for <oracle-l@orafaq.net>; Fri, 14 Feb 2003 15:58:55 -0600
X-ClientAddr: 209.68.248.164
Received: from newsfeed.cts.com (newsfeed.cts.com [209.68.248.164])
 by ensim.rackshack.net (8.11.6/8.11.6) with ESMTP id h1ELwsQ06640
 for <oracle-l@orafaq.net>; Fri, 14 Feb 2003 15:58:54 -0600
Received: from fatcity.UUCP (uucp@localhost)
 by newsfeed.cts.com (8.9.3/8.9.3) with UUCP id KAA97181;
 Fri, 14 Feb 2003 10:42:29 -0800 (PST)
Received: by fatcity.com (26-Feb-2001/v1.0g-b72/bab) via UUCP id 0054DE83; Fri, 14 Feb 2003 09:44:02 -0800
Message-ID: <F001.0054DE83.20030214094402@fatcity.com>
Date: Fri, 14 Feb 2003 09:44:02 -0800
To: Multiple recipients of list ORACLE-L <ORACLE-L@fatcity.com>
X-Comment: Oracle RDBMS Community Forum
X-Sender: "Godlewski, Melissa" <Melissa.Godlewski@hq.doe.gov>
Sender: root@fatcity.com
Reply-To: ORACLE-L@fatcity.com
Errors-To: ML-ERRORS@fatcity.com
From: "Godlewski, Melissa" <Melissa.Godlewski@hq.doe.gov>
Subject: RE: Database naming conventions
Organization: Fat City Network Services, San Diego, California
X-ListServer: v1.0g, build 72; ListGuru (c) 1996-2001 Bruce A. Bergman
Precedence: bulk
Mime-Version: 1.0
Content-Type: multipart/alternative;  boundary="----_=_NextPart_001_01C2D450.A06E98B0"
------_=_NextPart_001_01C2D450.A06E98B0
Content-Type: text/plain; 
 charset=iso-8859-1
Content-Transfer-Encoding: 7bit

Thanks,   I Talking about the SID. 

I got my smile for the day, putting version etc. in would certainly add to
the absurdity.

-----Original Message-----
Sent: Friday, February 14, 2003 11:59 AM
To: Multiple recipients of list ORACLE-L


Are we talking SID or connect string?  I seem to remember that there was (or
is on certain OSs) a limit to the length of the SID - so I tend to keep the
SIDs short and sweet.  If it is the connect string - then who is it that
needs to know it is an Oracle database?  The user?  Why?  The DBA?
Er...shouldn't he/she already know that?  
I agree with you - I would eliminate the 'ora'.  You can illustrate the
absurdity by insisting that it also include the version number and OS
ora9201tru64p24x7.



Jay Hostetter
Oracle DBA
D. & E. Communications
Ephrata, PA  USA

>>> Melissa.Godlewski@hq.doe.gov 02/14/03 11:23AM >>>
List, 
 
I'm use to using a standard D=development T=test P=production.  So for a
database newly created on development it would be called something like
D24X7.  Then when it was created on Production it would be called P24X7.  Or
along similar lines.
 
I'm working with an other DBA who wants everything to start with ora.
Therefore it would be called orad24x7 and orap24x7.  I've argued the ora is
rather redundant since everyone will know it's an Oracle database they are
connecting to.  He is adamant it should have the ora identification so it is
easily identified.  I feel it will cause more confusion having ora at the
beging of every dbname.  
 
Any thoughts for against either position?
 
TIA
M.Godlewski
 
 
 
 



**DISCLAIMER
This e-mail message and any files transmitted with it are intended for the
use of the individual or entity to which they are addressed and may contain
information that is privileged, proprietary and confidential. If you are not
the intended recipient, you may not use, copy or disclose to anyone the
message or any information contained in the message. If you have received
this communication in error, please notify the sender and delete this e-mail
message. The contents do not represent the opinion of D&E except to the
extent that it relates to their official business.
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jay Hostetter
  INET: jhostetter@decommunications.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru@fatcity.com (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).


------_=_NextPart_001_01C2D450.A06E98B0
Content-Type: text/html; 
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: Database naming conventions</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Thanks,&nbsp;&nbsp; I Talking about the SID. </FONT>
</P>

<P><FONT SIZE=3D2>I got my smile for the day, putting version etc. in =
would certainly add to the absurdity.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Jay Hostetter [<A =
HREF=3D"mailto:jhostetter@decommunications.com">mailto:jhostetter@decomm=
unications.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, February 14, 2003 11:59 AM</FONT>
<BR><FONT SIZE=3D2>To: Multiple recipients of list ORACLE-L</FONT>
<BR><FONT SIZE=3D2>Subject: Re: Database naming conventions</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Are we talking SID or connect string?&nbsp; I seem to =
remember that there was (or is on certain OSs) a limit to the length of =
the SID - so I tend to keep the SIDs short and sweet.&nbsp; If it is =
the connect string - then who is it that needs to know it is an Oracle =
database?&nbsp; The user?&nbsp; Why?&nbsp; The DBA?&nbsp; =
Er...shouldn't he/she already know that?&nbsp; </FONT></P>

<P><FONT SIZE=3D2>I agree with you - I would eliminate the 'ora'.&nbsp; =
You can illustrate the absurdity by insisting that it also include the =
version number and OS ora9201tru64p24x7.</FONT></P>
<BR>
<BR>

<P><FONT SIZE=3D2>Jay Hostetter</FONT>
<BR><FONT SIZE=3D2>Oracle DBA</FONT>
<BR><FONT SIZE=3D2>D. &amp; E. Communications</FONT>
<BR><FONT SIZE=3D2>Ephrata, PA&nbsp; USA</FONT>
</P>

<P><FONT SIZE=3D2>&gt;&gt;&gt; Melissa.Godlewski@hq.doe.gov 02/14/03 =
11:23AM &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>List, </FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>I'm use to using a standard D=3Ddevelopment T=3Dtest =
P=3Dproduction.&nbsp; So for a</FONT>
<BR><FONT SIZE=3D2>database newly created on development it would be =
called something like</FONT>
<BR><FONT SIZE=3D2>D24X7.&nbsp; Then when it was created on Production =
it would be called P24X7.&nbsp; Or</FONT>
<BR><FONT SIZE=3D2>along similar lines.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>I'm working with an other DBA who wants everything =
to start with ora.</FONT>
<BR><FONT SIZE=3D2>Therefore it would be called orad24x7 and =
orap24x7.&nbsp; I've argued the ora is</FONT>
<BR><FONT SIZE=3D2>rather redundant since everyone will know it's an =
Oracle database they are</FONT>
<BR><FONT SIZE=3D2>connecting to.&nbsp; He is adamant it should have =
the ora identification so it is</FONT>
<BR><FONT SIZE=3D2>easily identified.&nbsp; I feel it will cause more =
confusion having ora at the</FONT>
<BR><FONT SIZE=3D2>beging of every dbname.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Any thoughts for against either position?</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>TIA</FONT>
<BR><FONT SIZE=3D2>M.Godlewski</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>**DISCLAIMER</FONT>
<BR><FONT SIZE=3D2>This e-mail message and any files transmitted with =
it are intended for the use of the individual or entity to which they =
are addressed and may contain information that is privileged, =
proprietary and confidential. If you are not the intended recipient, =
you may not use, copy or disclose to anyone the message or any =
information contained in the message. If you have received this =
communication in error, please notify the sender and delete this e-mail =
message. The contents do not represent the opinion of D&amp;E except to =
the extent that it relates to their official business.</FONT></P>

<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Please see the official ORACLE-L FAQ: <A =
HREF=3D"http://www.orafaq.net" =
TARGET=3D"_blank">http://www.orafaq.net</A></FONT>
<BR><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Author: Jay Hostetter</FONT>
<BR><FONT SIZE=3D2>&nbsp; INET: jhostetter@decommunications.com</FONT>
</P>

<P><FONT SIZE=3D2>Fat City Network Services&nbsp;&nbsp;&nbsp; -- =
858-538-5051 <A HREF=3D"http://www.fatcity.com" =
TARGET=3D"_blank">http://www.fatcity.com</A></FONT>
<BR><FONT SIZE=3D2>San Diego, =
California&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mailing list =
and web hosting services</FONT>
<BR><FONT =
SIZE=3D2>---------------------------------------------------------------=
------</FONT>
<BR><FONT SIZE=3D2>To REMOVE yourself from this mailing list, send an =
E-Mail message</FONT>
<BR><FONT SIZE=3D2>to: ListGuru@fatcity.com (note EXACT spelling of =
'ListGuru') and in</FONT>
<BR><FONT SIZE=3D2>the message BODY, include a line containing: UNSUB =
ORACLE-L</FONT>
<BR><FONT SIZE=3D2>(or the name of mailing list you want to be removed =
from).&nbsp; You may</FONT>
<BR><FONT SIZE=3D2>also send the HELP command for other information =
(like subscribing).</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2D450.A06E98B0--

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Godlewski, Melissa
  INET: Melissa.Godlewski@hq.doe.gov

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru@fatcity.com (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).

