Sticking with SQL Server 2005 or 2000

What if you don't need change?

These days, change seems to be everywhere but in my pocket. In this year’s US presidential campaign, I heard a lot about change. And now, I can’t escape the ever-increasing talk about upgrading to SQL Server 2008. So I’ve drawn a line in the sand: Just because something’s new, you don't have to leap to adopt it. You need to carefully compare SQL Server 2008 to the version that you're running now, whether it's SQL Server 2005 or SQL Server 2000. Even if you decide not to upgrade, still has the information you need to keep you going with whatever SQL Server version you have. And unlike some political slogans, these are solutions you can believe in. I promise.


SQL Server 2005:

“SQL Server 2005 Resources,” InstantDoc ID 97839

“Leverage Reporting Services 2005 Independent of Your Database,” InstantDoc ID 48629

“SQL Server Consolidation,” InstantDoc ID 95461

“SQLQueryStress,” InstantDoc ID 97906

“Best Practices Analyzer,” InstantDoc ID 95383


SQL Server 2000:

“Bare-Metal Tuning,” InstantDoc ID 46492

“Moving Cubes from Analysis Services 2000 to 2005,” InstantDoc ID 95161

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.