THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Kalen Delaney

Did You Know? Microsoft is/are Still Fixing Bugs On SQL Server 2005

I taught a private class last week near Portland (Oregon) and although the company has a lot of SQL Servers, there was not much excitement at all about SQL Server 2008. They still have many SQL Server 2000 installations, and are debating whether to upgrade those to 2005. Most of the interest was in the real value of the new 2005 features, like partitioning, and the new large object types, as well as interest in the new metadata, such as the DMVs.

They're trying to run a business, and keep their systems running well. They don't have a lot of time to get excited about features that are way in the future.

I can't believe that my client is the only organization that is very interested in the continued health of SQL Server 2005, but I was surprised to see no blog posts here on SQLBLOG about the latest Cumulative Update for SQL 2005.

Yesterday, Microsoft released CU#8 and you can read about it here:

http://support.microsoft.com/kb/951217

So what are you waiting for?

~Kalen

Published Tuesday, June 17, 2008 10:45 AM by Kalen Delaney

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

James Luetkehoelter said:

Good point Kalen. I've got a lot of clients that are really clinging to 2000, with no intention on moving (to 2005 much less 2008). The *still* have learning to do on the 2000 platform (which I'm sure you experienced last week).

Heck, I still know someone running 4.2!

June 17, 2008 1:36 PM
 

Adam Machanic said:

Hi Kalen (and readers),

If you check out our roller ( http://sqlblog.com/roller/roller.aspx ) you will see at least one post on the topic :-)

I try to keep all of the top external SQL Server blogs in the roller, so between both our main feed and the roller feed we get a pretty complete cross-section of what's happening in the SQL Server world.

June 17, 2008 1:37 PM
 

Hugo Kornelis said:

Hi Kalen,

>> So what are you waiting for? <<

A fully supported service pack, perhaps?

Best, Hugo

June 17, 2008 6:49 PM
 

alphatross said:

SQL 2005 CU 8 - this is what I'm waiting for (from KB 951217):

"This cumulative update package may receive additional testing. Therefore, if you are not severely affected by any of these problems, we recommend that you wait for the next SQL Server 2005 service pack that contains the hotfixes in this cumulative update package."

In other words, only install CU8 if it contains a fix for a specific issue you are experiencing, otherwise wait for the next Service Pack. I've heard Microsoft consultants and SQL Experts often advise to install the latest updates for SQL Server, but if you actually press Microsoft for something in writing they will stick to the above policy.

June 17, 2008 6:52 PM
 

sql_noob said:

when we upgraded to 2005 we had some problems like a query running for 10 minutes and locking up the server. and MS support was pretty bad last year because everyone was calling and they were swamped.

i bet people are afraid of sql 2008 because there will be problems and no one wants downtime

June 18, 2008 11:05 AM
 

J. Morgan Smith said:

And now... Cumulative Update 9!!!!

http://support.microsoft.com/default.aspx?scid=kb;en-us;953752&sd=rss&spid=2855

I have 2000 clients that are going to bypass 2005 altogether and jump right to 2008, then I have others that just upgraded to 2005 and have no intention of looking at 2008 or another couple of years.

June 18, 2008 1:59 PM
 

alphatross said:

Note that CU 9 is not yet "official" and is referred to as a "Build In Progress" here: http://support.microsoft.com/kb/937137/LN/

So stick with CU 8 if you have a policy of installing latest Post-SP updates.

June 18, 2008 8:31 PM
 

MikeS said:

It’s the existing non-critical databases we wish to keep humming along and supported on SQL2000 and 2005.  Who wants the headache of revalidating 100s of non-critical applications using shared SQL Servers with 100s or 1000s of databases?  Our development resources are booked solid on *new* projects – few are looking back at old SQL projects so there is little incentive to migrate old projects to newer SQL versions while SQL 2000 SP4 remains on Extended Support until April/2013.

June 21, 2008 8:27 PM
 

BrianC said:

We are going to finally bite the bullet and install CU8 on top of our SQL 2005 SP2 installation. Things generally work well now, but there is at least one bugfix that we will benefit from. I hope this won't be a mistake....

Also, try running the most recent version of Microsoft's SQL Server Best Practices Analyzer. We did and it actually recommended installing CU4 (or greater) based on what it found when analyzing our database servers.

June 23, 2008 5:15 PM
 

Chris Wood said:

is this the rule that BPA complained about: -

On versions of SQL Server before 9.0.3171.0, a known issue can degrade query performance on 32-bit and 64-bit systems with 2 gigabytes (GB) or more of memory.

June 24, 2008 2:05 PM
 

tduffy77 said:

A fully supported Service Pack

June 26, 2008 5:25 PM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

Favorite Non-technical Sites or Blogs

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement