Here are the points you should consider when naming your database objects:
- The name follows the existing standards and practices in place. Inventing new standards isn't helpful; enforcing existing standards is.
- The name clearly describes the role or table contents.
- For major tables, use short, powerful names.
- Name lookup tables after the table to which they are linked, such as account_status.
- For associative or linked tables, use all the names of the major tables to which they relate, such as customer_account.
- Make sure that the name is clearly distinct from other similar names.
- Use consistent abbreviations.
- Use underscores. Casing is not preserved by default, so using CamelCase names, such as customerAccount, as used in Java ...