My optimization rules of thumb for a slow running query: read the query plan first, turn scans into seeks, fix bookmark lookups with a covering index and more.
SQL SERVER – 15 Best Practices for Better Database Performance
Best practices for better Database Performance: keep only needed data, normalize tables, use lookup tables and small primary keys. I list 14; you suggest the 15th.
A Self-Review Checklist for Stored Procedure Changes
Use a self-review checklist for stored procedure changes: realistic data, plans, IO, NULL inputs, clean rollback, and a ready recovery script.
What to Alert On, and What to Let Sleep
Make SQL Server alerting actionable by tying thresholds to impact, checking missing work, reducing duplicates, and reviewing every overnight call.
Reading SQL Server Error Messages Carefully
Reading SQL Server error messages carefully means using number, severity, state, and line to narrow the cause before searching.
Reading the SQL Server Error Log Properly
Read the SQL Server error log for startup details and incident context, filter it with T-SQL, and cycle files without losing needed history.
Checking XACT_STATE Before COMMIT or ROLLBACK in a CATCH Block
XACT_STATE separates transaction validity from the decision to retain work. Two isolated examples show a doomed transaction and a committable one, both with deliberate errors. Clean up on the same connection and respect the caller’s transaction ownership.