Why we archive slow threads instead of deleting them
Community memory matters for SQL tuning—here is how moderators keep searchable history without drowning newcomers.
Quiet signals from production clusters, shared calmly in threads instead of midnight pings.
- 7 seasons hosting live plan reviews
- 38 moderated channels across engines
- 2.1k learners completing labs since launch
- 140 office-hour blocks logged last year
- 12 cities represented in the latest cohort map
Guides on duty
Early mornings belong to indexing mentors; midweek peaks belong to execution-plan coaches; late evenings rotate to bottleneck diagnosticians so every timezone hears a human voice. The forum archive grows chronologically like a workshop wall—each moderator curates a ribbon of solved threads newcomers can replay without feeling late to the party. We promote forward-looking prompts: what will break next release, not who failed last night.
“The Index Strategy Studio workbook is pinned above my desk—the partial-index flowchart alone saved a messy rollout.”
★★★★★ Verified learner — Night School pacing respected our on-call rotation.
“Bottleneck Signals Lab forced us to document waits before jumping to index changes—small habit, big calm.”
Mixed notes: loved the async incident writeups; wanted one more Postgres-specific latch example (coach shipped it three days later in a pinned addendum).
Parallelism Guardrails finally gave us a shared MAXDOP experiment log the infra team did not roll their eyes at.
You belong in the slow-query thread
Members trade annotated plans, not egos. Whether you steward Postgres or SQL Server, the identity here is curiosity with receipts.
Values
Evidence first — every claim in a thread should carry a plan fragment or measurement snippet. Kind directness — critique the query shape, not the author’s career choices. Rotation over heroics — moderators model sustainable pacing so learning survives busy quarters.
Search the handbook slices
- Pick a documentation slice from the menu.
- Press your engine name plus a symptom keyword.
- Open the matching pinned explainer thread.
Join flow
- Pick a display name, verify your email, and acknowledge the code of conduct. Moderation is lightweight but real—we want earnest learners, not drive-by spam.
Pinned field notes
Notebook etiquette for plan screenshots
Crop thoughtfully, label versions, and avoid leaking hostnames—our posting checklist for plan images.
Office hours pacing across time zones
How we rotate live sessions so Seoul, Berlin, and Chicago members all get a fair shot at live coaching.
Readable postmortems beat hot takes
A short template we use when closing a tuning thread so the next reader understands what actually changed.