Not "TICK" as in "Deer-" or "Wood-" (which look like corn kernels with legs
when they dig in and suck your blood), but as in "- vs. The Uncommon Cold",
"- and Arthur", and "SPN!".
http://www.thetick.ws/
:)
Now back to naming new databases...
Rich
Rich JesseSystem/
Raj
TICK does not stand for anything so interesting or pleasant in
Wisconsin.
Sorry Rich, just a little upper midwestern humor.
Dennis Williams
DBA, 40%OCP, 100% DBA
Lifetouch, Inc. Eden Prairie, Minnesota.
[EMAIL PROTECTED]
-Original Message-
Sent: Friday, February 14, 2003
Title: RE: Database naming conventions
We do have a TICK ... it stands for sportsTICKer ...
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn&#
Title: RE: Database naming conventions
Thanks
everyone for your opinions. I believe I have some good examples of why not
to use ora.
This
list is great!
-Original Message-From: Jamadagni, Rajendra
[mailto:[EMAIL PROTECTED]]Sent: Friday, February 14, 2003
3:59 PMTo
Now my left-brain is arguing with the right-brain. Some of our test/dev DBs
are (or have been):
MULTI, ARENA, ORBIT, RALLY, and EMPIRE
(the word "playground" was too long...) And I've created at one point or
another:
DUPLO, AMIGA, PLINK, CHEWY, HOPS, EDGE, ENCLAVE, and TICK.
No one's really a
Title: RE: Database naming conventions
We use following syntax ...
* FAM -- ABC Family Production DB
* OLDFAM -- essentially FAM but as of 2AM today (refreshed daily or on demand)
* FAMQA -- FAM QA
* FAMTEST -- FAM User Acceptance
* FAMDEV -- Fam development
This works good for
This reminds me something that happened to me about seven years ago. We had
a head honcho (read DBA manager) who just had a sweet slide from DB2 word to
Oracle and as one of the first things he suggested was to rename all the
tables to be prefixed by "USERTAB_" and all the views by "USERVIEW_", and
Melissa,
Ask him if he name all his tables "TAB...", java class "Java...",
his pet "CAT..." or "DOG..." etc?
Richard
-Original Message-
Sent: Friday, February 14, 2003 1:44 PM
To: Multiple recipients of list ORACLE-L
there is no reason to call the database "ora."
I understand the
Title: RE: Database naming conventions
how about just an 'o'
od24x7
op24x7
you could then use 'u' for udb and 'm' for MySQL, and 's' for SQL Server.
-Original Message-
From: Rachel Carmichael [mailto:[EMAIL PROTECTED]]
Sent: Friday,
there is no reason to call the database "ora."
I understand the reasoning behind and the desire for naming
conventions.
What happens when your shop decides to go with MySQL (as this list has
been talking about)... will he want to rename the database to
mysqlt24x7? will he even be allowed to
Title: RE: Database naming conventions
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-
From: Jay Hostetter [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 14, 2003 11:59 AM
To
Melissa - You didn't mention which system you are on. My comments apply more
to Unix.
Oracle warns not to make the instance name too long. Formerly they
recommended you keep it to 4 characters. Not sure how that would apply
today. It does make your processes long.
My #1 objective is to make
I had
the same arguments with a consultant we had in at one time I compromised with
him. The database files are in a directory called 'oradata' and we use
a
designator of D development, T for Testing, B for Beta, P for Production
and S for Stress Test.
-Original Message-From: Godl
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
14 matches
Mail list logo
