A naming standard prescribes how databases, instances, tables, procedures, parameters, and other software elements are named. Its purpose is not cosmetic consistency: meaningful names make an environment and its code easier to identify, read, and maintain. Names should let a reader who knows the language infer what an object is trying to do. section 2.0 section 2.2
A memorable mistake is choosing short, generic names because they seem quick and harmless. Names such as SQL01, proc01, tbl03, updateStock, and stockUpdate force an investigator to inspect definitions before knowing which object is relevant. That lost time compounds during debugging, handovers, and production incidents. section 2.1 section 2.2
Use a naming standard to make intent visible without relying on comments alone:
- Choose descriptive object, procedure, and parameter names that distinguish purpose and role, such as billing versus delivery address or order quantity versus product ID. section 2.2
- Treat names as operational interfaces: select them so that object lists and procedure calls help a new maintainer locate the right target. section 2.2
- Plan instance names for organizational change. Names tied only to one application can become confusing when applications are consolidated; names tied only to departments can also break down after restructures. section 8.1
- Define the convention for the organization and deployment context rather than assuming one universal instance-name pattern fits every environment. section 8.1 section 8.11
Diagnosing an ambiguous stock update
An order procedure calls sp_stockUpdate with parameters named @product and @stock, although the called procedure treats them as quantity and product ID. Renaming them to @OrderQty and @ProductID, and using sp_updateProductStockLevel, exposes the intended operation before a debugger traces the code. section 2.2
Listing 2.1 Returning a list of stored procedures
SELECT
name
FROM sys.procedures ; #1
SELECT
name
FROM sys.objects #2
WHERE type_desc = 'SQL_STORED_PROCEDURE' ; #2
SELECT
name
FROM sys.objects #3
WHERE type = 'P' ; #3
List stored procedures first when investigating a database; descriptive names should make this inventory a useful starting point rather than a guessing exercise. section 2.2
