Handing over a database should include a current map, tested recovery path, access transfer, open risks, and a defined support period.
Finding Column Definitions Without the Documentation
Find column definitions in SQL Server with sys.columns, sys.types, and sys.all_columns, including length, nullability, and system objects.
Reading SQL Server Release Notes Before You Patch
Reading SQL Server Release Notes before patching helps you find known issues, fixes, behavior changes, and workload risks.
Writing a Good Technical Blog Post
A technical blog post works when it solves one problem with tested code, clear assumptions, a readable result, and honest limits.
Drawing a Diagram of an Existing Database
A diagram of an existing database starts with real foreign keys, uses SSMS to reveal relationships, and records the important paths a picture misses.
Documenting a Database With Extended Properties
Keep extended properties beside your SQL Server schema, maintain table and column descriptions, and query a useful data dictionary.
Onboarding a New DBA
Onboarding a new DBA starts with safe access, a server map, tested runbooks, and a first month of supervised operational tasks.







