SQL Server consulting for quick pain relief.

I’m Brent Ozar, and I’d like to help.

You’re frustrated with a slow, unreliable Microsoft SQL Server. You’re tired of hearing conflicting advice and watching team members point fingers at each other. Is it a storage problem? A code problem? A database problem? You just want clear answers. You’ve got a great team – but they just need some guidance to get back on track.

My 2-day SQL Critical Care® for $6,995 gets everyone on the same page and brings you permanent pain relief.

Leading up to the engagement: you install SQL ConstantCare® (it’s free for our clients), sending me diagnostic data, and getting the obvious recommendations out of the way. I track your wait stats, indexes, query plans, and more, looking for problems ahead of time so I can hit the ground running on Day 1.

Day 1 morning: we walk through your diagnostic data together. I start a WebEx session with your senior sysadmin or DBA, lead developer, and a business stakeholder. I show you what’s going on, training you as I go, showing you what we’re looking at. It’s a fast, low-impact, read-only process that I’ve used across hundreds of clients around the world, without any need for VPN logins or high-overhead traces. This is typically 8AM-noon Pacific.

Day 1 afternoon & day 2 morning: I write the findings. You go back to work while I analyze the data and build a plan of attack. I write a clear, actionable set of tasks for you to get permanent pain relief. You can see samples of ’em below.

Day 2 afternoon: I train your team. The moment of truth: we get back together to go through the findings in detail, showing you exactly why the SQL Server isn’t behaving the way you’d expect, and how to get the pain relief you want. It’s a mix of consulting and training: I’m showing you exactly what you need to do, and explaining why it’ll make a difference. You’re then empowered to relieve SQL Server pains on your own – without expensive prescriptions for ongoing consulting. (If you’d like to hire me to help do the work, though, that’s an option too.) This is typically noon-4PM Pacific.

Sample findings and past clients: ring any bells?

Performance Patient A: Slow Stuff – Patient A got in touch because they were having performance pain with a vendor’s applications. Patient A wasn’t sure if the problem was hardware, their SQL Server configuration, or the vendor’s code. Read Patient A’s findings PDF.

Performance Patient B: Diabolical Deadlocks – This company’s custom application had slowed down as their data grew. They’d tried several different relief efforts over time, but performance issues kept popping up – especially deadlocks. They wanted a permanent cure. Read Patient B’s findings PDF.

HA/DR Patient C: High Availability, Low Budget – After outages for multiple hours, they decided they needed a better answer than a single virtual machine. However, they didn’t want to burn Enterprise Edition money. Read Patient C’s findings PDF.

Ready to get started? Let’s talk.

Right now, my first weekday opening for a SQL Critical Care is June 1-2, 2020. I also have weekend availability at a $15K emergency rate, like Jan 4-5, Jan 11-12, or Jan 25-26.

If that works, you can book a free 30-minute sales call on my live calendar below.

Or, if you need something sooner, check with Erik Darling – he’s a former member of my team who launched his own consulting firm this year, and I’d recommend him highly.