Pre-code review tips for DBAs: why I check stored procedures on our development server every day for coding standards, with a link to my full article.
Why You Should Name Default Constraints
Name default constraints so deployments can find them reliably, and replace system-generated names through a reviewed migration.
Refactoring a Long Stored Procedure Into Readable Steps
Learn refactoring a long stored procedure with output baselines, named temp tables, dead-code removal, and two-way EXCEPT checks before release.
SQL SERVER – Recovery Models and Selection
SQL Server offers three recovery models: full, simple and bulk-logged. Here is when to select each one, based on how much data loss you can accept.
SQL SERVER – Database Coding Standards and Guidelines Part 2
Database Coding Standards and Guidelines Part 2: skip SELECT *, use SET NOCOUNT ON, prefer CTEs over temp tables, avoid cursors, and more query tips.
SQL SERVER – Database Coding Standards and Guidelines Part 1
Database Coding Standards and Guidelines Part 1: naming rules for tables, stored procedures, triggers, indexes, primary keys and foreign keys.
Coding Standards: A Short Guide and a Practical Naming Check
Useful SQL coding standards give teams a short rule set with clear exceptions. Run a read-only naming report, check literal underscores in procedure prefixes and review the results before changing objects.