SQL Server Naming Conventions and Standards

Estimated study time: 12 minutes. Consistent naming saves hours of confusion later.

SQL Server doesn't enforce a specific naming style, which means without a shared convention, a schema can quickly become inconsistent as more people contribute to it. Picking a standard early — and sticking to it — keeps a database easy to navigate.

Tables

Use plural, descriptive nouns: Customers, Orders, Invoices
Avoid prefixes like tbl_ — the object type is already clear from context
Use PascalCase or snake_case consistently, never both in the same database

Columns

Name columns clearly: FirstName rather than fn
Primary keys are often named Id or TableNameId (e.g., CustomerId)
Boolean-style columns should read like a question: IsActive, HasDiscount

Keys and Constraints

PK_Customers          -- Primary key
FK_Orders_Customers    -- Foreign key from Orders to Customers
UQ_Customers_Email     -- Unique constraint
CK_Products_Price      -- Check constraint

Stored Procedures and Views

usp_GetCustomerOrders   -- 'usp' = user stored procedure
vw_ActiveCustomers      -- views prefixed with 'vw'

💡 Tip: Avoid using SQL Server reserved words (like User, Order, or Group) as table or column names — they force you to use brackets everywhere, which clutters every query.

Why Standards Matter