Blog

After we signed a Microsoft Premier Support agreement at work, one of the first things we did was a Microsoft Exchange Health Check. A Microsoft guru spends a few days onsite using advanced custom tools to gather all kinds of information. The first result is a thorough report on your successes and failures at system management, and the second result is a set of action plans to help get the problems corrected. The Microsoft person has all kinds of experience from other big companies, which makes it really easy to get a jump start on the fixes. They can assist with some of the tougher problems, and they can give advice on what they’d conquer first.

We decided to bring them in for a SQL Server Health Check due to some performance problems we’d been having with our data warehouse. I’d researched the problems several times and kept coming back to the same conclusions, but since there were some political problems involved with the team relationships, we figured it would be good to get a completely independent opinion from outside. After all, it’s in Microsoft’s best interest to make sure their products perform, regardless of who’s right or who’s wrong.

Microsoft sent Abraham Samuel, a guy with a lot of relevant experience on ETL work in data warehouses. I can’t say enough good stuff about his abilities: he asked all of the right questions, figured out all of the right answers to our questions, and presented it all well. We learned a lot, corrected a few simple problems already, and made plans to do our own examinations on the rest of our SQL Servers. This week, I’m embarking on a two week mini-project to knock those out.

Bottom line: I was right about my performance diagnosis, muhahaha. Gotta love that.

In a few months, we’ll probably get another SQL Health Check. We’ll check two servers – the data warehouse to make sure the fixes did the fixing, and our new sales force automation cluster to make sure I’ve carried those same recommendations over across more servers.

I would highly recommend that anyone with a Premier Support agreement get a SQL Health Check. Even if you’re not having problems with your database servers, you’ll walk away with a useful set of knowledge about how to verify that everything’s functioning as it should.

It’s much less overhead and expense than a visit to the Microsoft Technology Center.

↑ Back to top
  1. Hello:

    From this article i see that “SQL Health Check” was done. Can you please break up this “SQL Health Check” how it was done & what was use tp do “SQL Health Check”. Without knowing how “SQL Health Check” was done, this article makes no sense.

    Thanks
    Jay

    • Hi, Jay. That’s a fair question, but it’s like asking a patient, “Well, how did the doctor give you a health check? What did he use to do it?” The patient isn’t in a position to understand what the doctor knows.

      However, I can tell you that the process involved two things: a lot of questions from Microsoft about our environment, and some very comprehensive scripts from Microsoft to evaluate our servers. Every script I saw was really impressive, and they did nail down some great findings.

      If you’ve got more questions about exactly how a health check is performed, consider contacting your Microsoft TAM and getting more information. They’ll be able to give you the rundown. If you don’t have a TAM, you’re not able to get a health check, but you could contact a company like Solid Quality Mentors to do a health check for you.

  2. Jay – a “SQL Health Check” is a standard offering from Microsoft. We send a consultant out to perform a series of tests specifically designed to evaluate the operation of your system. I’ll blog about this today over at http://blogs.msdn.com/buckwoody.

  3. Pingback: Buck Woody : The SQL Server Health Check

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

css.php