SQL Server Health Check

Rapid Diagnosis and Treatment Plan for SQL Server Problems

If you’re experiencing SQL Server problems or simply uncertain about the integrity or resilience of your database, our SQL Server Healthcheck will get you answers in three quick steps.


SQL Server health check clients will receive a $500 discount on a bucket of hours or $500 off for each of their first two quarters of our DBA as a Service engagement.


We ask you about your databases and SQL Server instance. What sort of data loss do you expect your system to allow? What keeps you up at night? Is someone receiving the alerts from your databases when they aren’t healthy?


We perform our detailed SQL Server Health Check that collects data about your databases, instances, and servers. Our team compares the findings with your expectations from the interview.


Within a week of the interview, we are delivering a full findings report in a follow-up meeting with you and your technical team. You get an action plan to remove the risks so you know for sure what’s right, what’s lacking, and how to make it all work.

Get Your Health Check Now

  • Let us know if you are currently experiencing any performance issues or have particular concerns.

100% “We’ll Make it Right” Guarantee!

We’re absolutely sure our SQL Server Health Check process provides immediate value to our clients. If at the end of the report delivery call and discussion you feel you haven’t received your money’s worth, let us know and we’ll refund your payment.

Our SQL Server Health Check Guarantee


We worked with Straight Path to have an outside expert review our SQL databases after discovering a considerable amount of corruption. We wanted to make sure that we were not at risk for data loss with an important customer, and we wanted assurance we were doing everything to ensure stability. The team at Straight Path were knowledgeable and thorough. They were flexible to our needs and schedules and we found them easy to work with. We’d recommend Straight Path to our clients and business partners.

Drew Wright, Director of Information Technology, DTIGlobal.com

We came to Straight Path Solutions for a SQL Server health check and we’re glad we did. During year-end processing, our teams were experiencing heavy delays running reconciliation reports. Despite our vendors insisting the solution was to buy more hardware and abandon virtualization, we suspected it was a database issue. Straight Path identified a lot of pain points that had inexpensive solutions. In no time, we were running year end reports and viewing invoices faster than we ever had – without the pain of expensive hardware upgrades. They’ve become trusted database advisors and they worked with us where we were.

Brian Gibson, President, Capital City Group

Case Studies

Customer One – “Are we going to lose our client’s data?”

We received a call from a software vendor who often escalates their support calls our way when there are tough database issues. Their customer had down databases and clients were supposed to be in their software working. They had errors about SQL Server corruption and weren’t sure what to do. Their customers relied on them for one thing – to keep their data safe and online. Had they failed? What could they do? We quickly engaged with them in the midst of these challenges. It turns out it was SQL Server corruption. Their storage system had caused it, and they were not prepared for it with alerting, corruption checks or a corruption-resistant recovery strategy. After a lot of consulting time, we had some good news, some mostly good news, and some bad news. We were able to use our experience along with a little luck and recovered the data in most of the corrupt databases. Two databases had partial data loss that we were able to quantify as data that wasn’t critical for customer operations in those databases, they lucked out, there. One database, though, was not recoverable and the only good backup wasn’t recent. They had to call their client and have the tough talk that started with “we’ve lost all of your data from the past quarter, but we have a backup from 3 months ago that had no corruption..” While corruption isn’t something that you can always prevent, it is something that this customer could have been prepared for and had we performed a SQL Server Health Check for them even a week before their call, the results would have been a minor nuisance and smaller expense than the recovery efforts and frustrating client conversation.

Customer Two – SQL Server Health Check with Corruption Risks Solved Calmly.

Another customer, also a customer of that same software vendor, reached out to us proactively for a health check. We did our normal process with them and in the execution of the health check, we noticed they were not prepared for corruption. From not checking their database integrity to not using a “Corruption Resistant” backup strategy or receiving any alerts, they were in a state sort of like that client above.

Thankfully, all of their databases passed our corruption checks. Along with many other findings relating to security best practices, and getting more performance out of their existing hardware with a few simple settings and changes, we helped them set up a proper schedule looking for signs and symptoms leading up to corruption. They ended up making some of the changes themselves from reviewing our report and being mentored through our review call, and they ended up engaging with us in a small bucket of hours to implement some of the more advance changes. Even with the small bucket of hours, this client saved money on our consulting over the first example, and they never had to have an awkward conversation with their customer.

Why Wait?

Maybe you have a perfect SQL Server environment. Maybe you don’t.

Are you sure where your SQL Servers fall on that continuum?

If you aren’t, how big of an investment is $1,497 to know for sure? You are pulled in a million directions, new installs and requests happen faster than you have the time to do that proactive look. Why not consider a health check to quickly prioritize where your SQL Servers stand and what risks are stored up on the horizon? Purchase a SQL Server Health Check today and we’ll be in touch within 1 business day to set up that initial call and begin collecting data shortly thereafter, and you can know for sure.

Remember, we take our guarantee seriously. So much of our business comes from referrals. We want you receiving the value we feel this check is. If you aren’t satisfied, let us know, we’ll make it right. Whether it’s a SQL Server Health Check or project work, we stand by it.

Still Aren’t Sure?

While the value of a good SQL Server health check such as our process far exceeds the cost and can often be recouped with the findings and a better future plan, we understand the value of being sure before spending. While you can look at our blog and about us and see all of our accolades and experiences, why not do a quick mini self-assessment while you make your decision? Check out a recent blog post about the various forms of SQL Server Health checks out there that you can do on your own. We really mostly just want your databases to be in good shape. We’d love to do that SQL Server Health Check for you, but we’re happy to see you taking the initiative all the same!

Download our free SQL Server self-assessment guide today. You can check your environment against the 8 most common “SQL Server killers” we encounter. These are the big ones that hurt the most. The findings we wish you discovered before calling for an emergency troubleshooting engagement. If you have the time to check these on all instances and you pass with flying colors? That’s a good sign. If you don’t? Well, there are a few things for you to start working on today.

Here are some of the questions you’ll be able to answer using this self-assessment:

  • Does SQL Server tell you when it’s not well?
  • Can you survive a loss of data or crash?
  • Are your databases free from corruption?
  • Are your databases self-tuning?
  • Is CPU power-saving keeping the brakes on your SQL Server deployment?
  • Are your SQL Servers secure?
  • Did you configure SQL Server after installation?
  • Do you keep up with SQL Server versions?