Oracle Naming conventions

Question

Hi everyone,
I wanted to ask you about Oracle Naming Conventions. I've found a lot of stuff on the internet. Here's a short summary of what I've discovered so far...
These are absolute:
1- All names should be between 1 & 30 characters (database names accept 8 characters max)
2- Names can not be duplicated in the same namespace
indexes, constraints... are in one "schema" namespace
tables views... are in another "schema" namespace
3- Only letters (lower & upper), numbers and $, # & _ are accepted in a name.
4- Quoted identifier are case sensitive and accept all kind of characters.
The previous rules can not be violated otherwhise the object won't be created.
Now they are a lot of naming conventions...
- Always use a plural names for table (USERS i.o. USER)
- use a prefix or suffix in constraint, indexes, ...
USERS_PK, USER_IDX...
I want to talk about these. What are your own naming conventions?
Thanks

Answer 1

user13117585 wrote:
Hi everyone,
Well actually I am currently trying to make a document for my company. All the developers will need to follow the rules I'm writing.
"It's good to be the king!"
My problem is that, I have many databases with hundreds schemas and I want to normalize everything (no only me want that but the management too). Anyway,
- Some people are still using only 8 letters for object names (tables, views, constraints...). Names are cryptic. I spend like an hour to understand what means DRPOLDSZ. And table columns are also limited to 8 characters (what could DELLOLCN mean??)
- Some developers are using other conventions. A good Table example would be:
TABLE DOSSIERS
DOS_DOSSIER_ID
DOS_NUMBER
DOS_CREATION_DATE
I hate that prefix in each column too;
As do I. Going back to data normalization .... the prefix adds nothing.
>
- Some developers use other conventions
some have table names in plural, others singular
some don't use the _ to separate multiple words object names, some well
some prefix table id some use postfix (id_table vs table_id)
etc etc.
I want to normalize all the databases to use one and only one convention; I already thought about it and wanted to know what you all have in place; how do you manage to have all your developers using the same conventions ?
About [ http://ss64.com/ora/syntax-naming.html| http://ss64.com/ora/syntax-naming.html] (1) article, I've read it but, I don't agree with the guy on everything. He mostly uses prefix (pk_Table, idx_table, fk_table). When you give some thoughts, isn't it better to use suffix?
Table_PK, Table_IDX, ...
When you do a query on ALL_ or USER_OBJECTS, you can order them on OBJECT_NAME and have the name groupped together.
I also prefer to have in the constraint name the base table and the referenced table. Instead of what the guy propose FK_TABLE_NAME, something like TABLE_NAME_REF_OTHER_TABLE_FK
Well, you don't have to slavishly follow anyone else's document. Again, you are using those for ideas. In the end, you need to do what makes sense to you. Also realize that having A standard - almost ANY standard - is better and more important that sweating the pros-and-cons of any particular detail. Just make a decision and go with it. Get management to sign off on it as the standard.
My question is not really a question but more a how do you handle all kind of developers and what is the best way to force them to normalize and use the same conventions...The only way to force it is to take "CREATE object" away from the developers. This is actually done in many shops. If you can't do that, then at least set yourself a task of auditing and going back to violators. If you get some recalcitrant violators, elevate it to management - who you had sign off on it.