Database Operations · SQL Server
SQL Server Care for Mixed Stacks
Four practical weeks for administrators inheriting a SQL Server estate alongside other engines — health checks, Always On listeners, and a sensible first month plan.
About this cohort
You arrive on a team and the first thing you find is a SQL Server you did not deploy. This cohort gives you a structured first-month plan for that exact situation. We work through baseline health checks with sp_Blitz and First Responder Kit scripts, untangle Always On Availability Groups without breaking listeners, and write maintenance plans that respect the actual recovery objectives of the business. You will also rehearse a clean handover: how to document what you found, what you changed, and what you would still touch if you had another sprint.
Inclusions
- Disposable SQL Server lab pre-loaded with a tangled inherited schema
- Walk-through of First Responder Kit and Ola Hallengren scripts
- Always On listener exercise across two replicas
- Maintenance plan worksheet aligned to RTO and RPO conversations
- Mentor review on your first-month handover document
By the end you can
- 01 Produce a credible first-month plan for an inherited SQL Server estate
- 02 Configure an Always On Availability Group listener and verify failover
- 03 Write a clear handover document that the next operator will read
Programme lead
Kim Da-eun
Lead SQL Instructor with twelve years of platform experience across retail and operational SaaS. She still rotates through on-call so the labs stay grounded.
Common questions
From the cohort
-
I walked in with three SQL Servers and no documentation. The handover template alone is worth saving as a personal artefact.
Soo-binSoo-bin
Inherited the estate · fintech ops team 4.7/5
-
Strong material, although the Always On lab needed an extra hour I did not have on a Wednesday night.
Ho-jinHo-jin
4.3/5 · survey