General - Do you know object name should follow your company Naming Conventions?
15/11/2019 8:50 AM by
- SQL Server Object Naming Standard.aspx SSW's Standard for naming SQL Server Objects.
- SQL Server Stored Procedure Naming Standard SSW's Standard for naming Stored Procedures.
- SQL Server Indexes Naming Standard SSW's Standard for naming Indexes.
- SQL Server Relationship Naming Standard SSW's Standard for naming Relationships
- Use decreasing generality for table names ie. Client and ClientInvoice, then ClientInvoiceDetail.
- Don't use underscores, instead use upper and lower case ie. ClientInvoice is preferred over Client_Invoice.
- Table names should not use plurals ie. Client is preferred over Clients.
- Generally don't use abbreviations. But there are a few words that are so commonly used that they can be abbreviated. These are:
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.Suffix Percent fields with 'Pct' ie. SalesTaxPct.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. What characters and symbols should I avoid using when naming objects in Access and SQL Server databasesDon't use reserved words on their own. ie. User, Count, Group, etc. They can be used if joined with other words. What are reserved words for SQL Server 2000?
- Quantity = Qty
- Amount = Amt
- Password = Pwd
Do you feel this rule needs an update?