Skip to main content -
It Looked Exactly Like a Bot Swarm. It Was SQL Server Parameter Sniffing.
-
The bot swarm that turned out to be one bad query plan
-
314 broken stats pages and one bad cursor
-
The Index Seek That Was Actually a Half-Table Scan (5000x, on a 4M-Row geoIP Table)
-
Measure the Bottleneck Before Blaming the Visible Workload
-
An Index Seek Can Still Read Far More Than You Expect
-
The decorative database: when your blocklist table isn't actually on the request path
-
The UA blocklist is the right-sized fix for an identified crawler (and the wrong one for a swarm)
-
The fix that ran on every request
-
A 25-Second Admin Screen Meant We Trusted the Wrong Query
-
The token-killing proxy I tested instead of trusting my own discipline
-
The Page Was Performing a Ceremony, Not a Job
-
Routing Logic That Does Work on the Way In: Redirect, Auto-Select, or Prompt
-
From 3.5 million round-trips to hundreds: batching a remap with temp tables