Guys,
So we talked about table naming conventions how about procedures, packages and functions....BTW, my organization did not want to drop type of object in name - except for tables. I know arguments against but for includes - preexisting standards and help for newer DBA's esp. during quick diagnostic exercise.
GENERAL NAMING CONVENTIONS
. Part of data model validation should be to ensure that no RDBMS reserved words are used.
. Recommended that models be checked against these standards as soon and as automatically as possible within design process to avoid unnecessary rework.
. Should have a common list of modifiers.
. Should have a common list of descriptors.
. Construction rules: - underscores can be used for clarity
TRIGGERS-prefix+modifier(s)+table name
FUNCTIONS-prefix+description of function
STORED PROCEDURES-prefix+description - description should contain clear description of process implemented.
PACKAGES-prefix (pkg?) + description.