Why You Should Perform a SQL Server Health Check
Things change in the database world every year; new standards, new versions, hybrid cloud solutions. So many moving parts and ways to save on license costs and increase efficiency.
Have you given your SQL Servers a health check?
Do you know what to look for?
Imagine knowing for sure what’s good in your SQL Server environment (and what isn’t) and having a plan to tackle the risks. Imagine the confidence of knowing that your data is safe, secure and performing as well as your clients demand.
A SQL Server Health Check Gives You Confidence
Our SQL Server health check has been proven time and time again. From the client who said, “I wish we knew you before we had the SQL Server corruption” to the client who no longer nervously anticipated their busy season with fear about performance, our health check process will give you the confidence of knowing what you don’t know, and knowing what to do about the risks.
More importantly, it will give you the keys to move forward. We don’t just dump our detailed findings analysis on your lap and run away. We’ll walk you through the resolution plan, make sure you understand the right priority to resolution and help you craft a “move forward plan.”
Here’s How Our SQL Server Health Check Works:
Step 1: Interview
We ask you about your databases. 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 get a picture of your challenges, needs, and fears and then work out access to your server.
Step 2: Checkup
We perform our complete 39-point SQL Server Health Check. This check collects data about your databases, instances, and servers. Our team reviews your servers, looks at your databases and compares the findings with your expectations from the interview. Finally, we write a comprehensive report outlining the challenges, issues, and needs for your short and long-term success.
Step 3: Follow-up
Typically within a week or two of the interview, we are delivering that full findings report in a follow-up meeting with you and your technical team. We’re giving you an action plan to remove the risks and giving you that confidence in knowing for sure what’s right, what’s lacking, and how to make it all work.
Ready to Find Out How Healthy Your SQL Servers Are?
Are you ready to know what is right with your SQL Server environment and what needs to change to keep your data secure, stable, available and performing like your clients demand and expect? Great!
Apply to receive a SQL Server Health check here. The price is $1,497, which is often easily recouped through increased server efficiency, a future reduction in SQL Server licenses or the prevention of a data loss disaster.
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.
Clients With Clean Bills of SQL Server Health
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.
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.
Still Aren’t Sure?
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?