You’ve probably seen that commercial where the chewing-gum company van stalks the guy who has been chewing the same piece of gum too long, and they attack him and make him chew another piece.
I feel like that with SQL Server 2000. Almost every shop I go into has at least one primary application running on SQL Server 2000. Now, don’t get me wrong – SQL Server 2000 is a fine piece of software engineering. From over TEN YEARS AGO. In “software time”, that’s like a thousand years or something.
While it was great for its day, the newer versions are faster, more secure, and more robust. And every time it doesn’t get upgraded, SQL Server is perceived as “not as fast/strong/etc” as other platforms (which are upgraded, of course).
Now, I’m not suggesting that anyone upgrade for upgrade’s sake. We all have work to do, and the last thing we need to do is change out a platform when there’s no need.
But there is a need. SQL Server 2000 isn’t in mainline support any more. That means it can be attacked easier and so on. And it doesn’t scale like the new offerings, nor does it have any of the new features the latest versions have.
“Oh”, you might say, “I don’t use those features anyway.” Well of course you don’t – you can’t if you still have SQL Server 2000! How do you know the ways you could help your organization if you don’t experiment with the new stuff?
But it isn’t the DBA I would chase down and steal gum from. It’s the vendors.
Every time I raise my eyebrows when I hear about the SQL Server 2000 installs, the DBA shrugs and says “The vendor won’t certify SQL Server X, so we have to stay at SQL Server 2000 or 2005.” And I say, that’s just lazy. Unless the vendor codes specifically for deprecated features, a simple test run during their software development should allow them to move forward. I’m not saying that’s an easy task, but certainly they’ve tested their software releases once in the last ten years, no? If not, doesn’t that make you nervous?
Anyhoo, spit out the SQL Server 2000. Or I might have to fire up the company van.
Thanks! I am forwarding a link of this page to clients.
Might want to look at the discussion on the mirror of this post over on SQLblog first:
Oops, wrong link!
Often the problem is not that the vendors don't support it, but that they only support it in their more recent software versions. Companies only have access to those later versions if they are paying maintenance fees and many of them refuse to pay them.
Therefore, a hurdle of upgrading the SQL server are the maintenance fees and penalties associated with the software which uses it.