Re-Evaluating Best Practices

SQL Server Best Practices
SQL Server Best Practices
I was reading a blog post from my friend Randolph West (b/t) on Best Practices and a thought struck me.

Best practices must constantly be reviewed/reevaluated as knowledge and technology changes.

Starting with Randolph’s definition of a best practice (he got it from Wikipedia and it’s more than good enough)

A best practice is a method or technique that has been generally accepted as superior to any alternatives because it produces results that are superior to those achieved by other means or because it has become a standard way of doing things, e.g., a standard way of complying with legal or ethical requirements.

Best practices are great. They give us a consistent starting point when setting things up. However not only are everyone’s requirements are different but they are ever changing as well. We have to keep in mind that a best practice is what works best most of the time and if it isn’t working in your situation you shouldn’t feel bad about changing it. Not only that, but best practices change over time. They have to.

If you go back a few years (~10) you’ll see best practices saying that your Page Life Expectancy should be 300 (5 minutes). Can you imagine that now? A quick look at some of the servers I work on and not one was under 150k (41 hours). Technology changed. Servers now have a great deal more memory than they used to. And in 10 more years the systems will have again shown a dramatic improvement. How about Max Degree of Parallelism. The best practice not that long ago was 0. Let your queries go as parallel as possible. Recently that’s changed. Now you might see 4 or 8 (as a starting point). This is because 10 years ago if you had 8 CPUs that was one heck of a system. Today servers with 64 CPUs isn’t that unusual.

Continue reading on

(0 votes. Average 0 of 5)
Leave a reply

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