SQL Critical Care®: Currently Accepting New Patients*

Our SQL Critical Care® for Microsoft SQL Server is the first step of resolution for any of the problems we solve. We check a SQL Server’s health, configuration settings, and bottlenecks, then dive into the databases, indexes, and queries.

Solve SQL pains in 3 days

We start by working with senior members of your team – typically a sysadmin, a DBA, and a developer. We examine the live server together, walking through troubleshooting queries, explaining things as we go. We capture screenshots and diagnostic information, and we use that to build customized action plans and training presentations.

We finish with a group session with all affected people (DBAs, developers, project managers) walking through the findings, explaining why they were an issue, and we teach the whole team how to avoid upcoming pains, too.

For just $6,995, you can stop the confusion and get real answers with actionable, prioritized homework. Your team even gets access to our online training video classes to keep you in great shape moving forward, because we’ll assign them video homework that specifically relates to the problems you’re facing.

Sample findings: ring any bells?

Here’s a few sample deliverables from past engagements – one of ’em might match up with a scenario like yours:

Patient A SQL Critical Care Findings (1)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 something in the vendor’s app code. The software vendor wasn’t sure either, but they were pretty sure it wasn’t their code. Patient A also wanted help with maintenance and an overall checkup. Read Patient A’s findings PDF.

Patient B SQL Critical Care Findings (1)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.

Patient C SQL Critical Care Findings (1)HA/DR Patient C: AlwaysOn Often Off – This patient called us because their AlwaysOn Availability Groups in Amazon Web Services weren’t really always on – more like kinda sorta on. They were failing over at apparently random times. They had a team of developers and sysadmins, and a couple of them were decent at database administration, but they didn’t have full time DBAs. Read Patient C’s findings PDF.

Our SQL Server medical team*

Our SQL Server paramedics

Our SQL Server paramedics

We have an ambulance full of SQL Server pros. Between us, we have decades of SQL Server experience, multiple Microsoft MVP awards, and many other certifications and awards from Microsoft for our technical excellence and contributions to the community. Your own staff probably already reads our blogs, watches our free webcasts, attends our conference presentations, and uses our scripts in production.

* No one at Brent Ozar Unlimited holds a medical degree. If you have joint pain, breathing problems, or other symptoms, please call your doctor. If you have SQL performance issues, that’s what we’re here for.

Ready to get started? Book your free 30-minute sales call.

We’ll discuss your pains, how we can help, and our next availability.