Oracle Naming Conventions
Many Fortune 500 companies rely heavily on custom-built applications and have a large internal IT department of their own.
They generally tend to build their own standards and naming conventions. This helps bring large development teams on common grounds,
and it is very easy for any person on the team to understand as well as reuse code.
These companies enforce naming conventions and standards through walkthrough.
Many other companies rely entirely on the standards recommended in the documentation that comes with a development tool.
This is also a very effective, fast, and cost-efficient way to build standards for your applications.
Companies that outsource their IT efforts generally seem to adopt this approach.
Oracle DBA's must pay careful attention to the structure and naming conventionswithin the database.
All applications will reside within the same schema owner and naming conventions will be used to
identify table/index components:
Oracle Schema Naming Standards
The following standards will be used in all schemas:
- Schema objects: All non-table schema objects will be prefixed by their type and all index names will begin with idx, and all constraint names will begin with cons.
- Referential Integrity conventions: All tables will have full RI, including PK constraints, FK constraints and check constraints.
The default for foreign key constraints will be "On Delete Restrict", unless otherwise specified.
This means that no parent record can be deleted if there are corresponding child records.
- Primary keys: Oracle Sequences will be used to generate unique row identifiers and all sequence numbers generally will start at one and increment by one.
- Check Constraints: Lists of valid values will be used in all cases to restrict column values and validity