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.

Andy Leonard (2/8/2010)

---

Great editorial Grant!

This reminded me of the demise of my checklist. I used to think database tuning was a matter of checking off items on my checklist, in order, as I made corrections. I believed this until some of my changes took a server to its knees.

Investigation revealed the checklist wasn't the problem - my faith in it was the problem.

I'd built the checklist from experience. I went back to that experience and instead documented the methodology I'd used to gather measurements and create tests. This methodology replaced my checklist.

:{> Andy

Grant Fritchey (2/8/2010)

Now that sounds like a great presentation. When are you giving it?