• Tobar (2/8/2010)


    Great Article.

    Each person must assess their own needs and responses when considering "cookie cutter" numbers. As much as we would like to believe, we are not a one size fits all creature. But we like to think that way. The human body is infinitely more complex than a database, but the same rule applies. Too often after implementing a cookie cutter number, people/DBAs only question the number if things go badly, and there is nothing wrong with that, but that doesn't mean it is the wrong number for everybody else. We hope that the "experts" know what they are talking about, and mostly they do. That is not to say that through research you can not come up with a better number for the situations you are in.

    Thanks, and I agree with you. If you really dig, probably, each and every measurement is unique to a given situation, but the variation may be very slight, so does it matter that your disk queue length is 4.5 or 5 before you start get a little concerned? But sometimes, those measurements can vary wildly from one situationn to another. The more you know, the better you'll be able to understand if the measurement applies in your situation. The problem is, there's a lot to know.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning