Independent SQL Server performance consulting — I find what's dragging your database down, fix it, and keep it fast as you grow. Tuning, indexing, and query optimization, done by someone who's spent a decade in production.
Nearly every performance problem I'm called in for comes down to one of these three things — or all of them at once. It's the whole focus of the practice.
The full-picture work: reading wait stats and execution plans to find why the server is struggling under load, then fixing the configuration, contention, and bottlenecks that show up when real traffic hits. This is where a slow, unpredictable database becomes a fast, steady one.
Indexes are the single biggest lever on SQL Server performance — and the easiest to get wrong. I design the right ones, add covering and INCLUDE columns where they earn their keep, and clear out the redundant indexes quietly dragging down every write. Done well, this is what makes reads fast without punishing everything else.
The code layer: rewriting the expensive queries, stored procedures, and views that dominate your workload. I work from the execution plan to cut the reads, kill the implicit conversions, and reshape the T-SQL so the same result costs a fraction of the resources — often the fastest win of the three.
Ten years ago I was a software engineer, and my company needed someone to go deeper on the database side. I took a few classes to fill the gap — and fell for it almost immediately. Databases are genuinely complicated, but they're objective: there's a real answer under the problem, and the work is finding it. That's the part I loved then, and still love now.
A decade later, I've spent that time going as deep as I can — tuning performance, designing indexing, and optimizing queries on production SQL Server running real, high-transaction workloads where slow meant lost revenue. I still treat every engagement the same way I treated that first class: there's an answer in here, and I'm going to find it.
Excellent work cleaning up the database and consolidating functionality down to a single point, so we don't have duplication all over. He's making real progress toward maintainable code. He should continue being a DBA bad ass.
Jesse is very responsive to any database issues I have. He's always looking for ways to optimize our system and track down problem spots.
I was really impressed with how he built our workspace query-performance improvements in an extensible fashion, allowing more optimizations to be added later. Well implemented.
No forms, no sales funnel — just an email and an honest answer.
Send me a short email describing the problem — the symptom, roughly your scale, and how urgent it is. That's all I need to start.
I'll email you back with an honest read on whether it's something I can fix. If it is, we'll schedule a short call to talk through it in more detail.
From there, most engagements start with a fixed-price performance assessment — I dig into your server and hand you a prioritized set of fixes, before any bigger commitment.
A query that's dragging, a database that's buckling under load, indexing you suspect is a mess — send a short description and I'll tell you honestly whether I can help.