Get Your Memory Back!!
-
Are you a SQL Server 2000, AWE user? If so, you're probably glad to have this hotfix. Did you know if you moved to SP4 that SQL Server could only use half of the computer's memory?
What if you convinced your boss to buy a nice big 16GB server so you could have 14GB set aside for SQL Server and have screaming queries. Then you get an outage window to apply SP4 after it's been tested on your great 4GB server with all your apps. Everything was cool, so you applied the patch and went home to enjoy the weekend.
Probably some time Monday mid morning or early afternoon the screams started. And the phone started ringing. And if you were sharp and on the ball, you probably found SQL was only running on 8GB of RAM. Hopefully that didn't stump you too long before you called Microsoft and got the bad news: it was an SP4 bug. I just have one question.
How could this get through QA?
I mean I know how, someone didn't test for it, but how can a service pack reduce memory usage and no one realize it? It's not as bad as a security bug, but this is some big egg-on-face. Especially to the people that really matter for revenue: companies that buy big servers.
In other news Developer.com chose SQL Server 2005 as their Database Product of the Year. Is 2005 winning in 2006 amusing to anyone else? I'm sure most of you know I'm dubious of product awards, especially when they're vote driven. This one is no exception, but I am surprised that a website that has so much Java and non-Microsoft technology and tools would have SQL Server win.
-
Well it's good for someone maybe that just ran across this but this is OLD information and hopefully anyone setting up or Administering a SQL 2000 on 2000 w/SP4 has already read about and taken care of this.
Thanks though for the article to wake some people up.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply