General - Do you know object name should follow your company Naming Conventions?
  v4.0 Posted at 19/03/2020 11:03 AM by Christian Morford-Waite
  1. ​​SQL Server Object Naming Standard SSW's Standard for naming SQL Server Objects.
  2. SQL Server Stored Procedure Naming Standard SSW's Standard for naming Stored Procedures.
  3. SQL Server Indexes Naming S​tandard SSW's Standard for naming Indexes.
  4. SQL Server Relationship Naming Standard SSW's Standard for naming Relationships
  5. Use decreasing generality for table names ie. Client and ClientInvoice, then ClientInvoiceDetail.
  6. Don't use underscores, instead use upper and lower case ie. ClientInvoice is preferred over Client_Invoice.
  7. Table names should use pluralisation ie. Clients is preferred over Client.
  8. Generally, do not use abbreviations. But there are a few words that are so commonly used that they can be abbreviated. These are:
    • Quantity = Qty
    • Amount = Amt
    • Password = Pwd
  9. Prefix all Date fields with 'Date' ie. DateInvoiced. One extra use of this is you can have generic code that enables a Date control on this field.
  10. Suffix Percent fields with 'Pct' ie. SalesTaxPct.
  11. Only use alphabet characters. ie. don't use AustraliaListA$. Avoid the following characters in your object names in SQL Server. If you do not do this, you will need to constantly identify those ill-named objects with bracketed or quoted identifiers - otherwise, unintended bugs can arise.
  12. Don't use reserved words on their own. ie. User, Count, Group, etc. They can be used if joined with other words. Reserved Keywords (Transact-SQL)

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address: