Release Service Pack 3 for SQL Server 2005 - by Hugo Kornelis

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 326575 Comments
Status Closed Workarounds
Type Suggestion Repros 1215
Opened 2/1/2008 11:42:15 AM
Access Restriction Public


Since Service Pack 2 was relelased, numerous bugs have been fixed. They are available in cumulative update packages (6 to date). However, Microsoft recommends customers not to install these cumulative updates unless affected by one of the fixed bugs. That creates a dilemma for SQL Server administrators. You do not want to install a package if Microsoft recommends against it, but you also want to take pro-active action so that you can squash the bug BEFORE it affects you.
Sign in to post a comment.
Posted by Microsoft on 7/24/2009 at 10:57 AM
SQL 2005 SP3 has been released. Here is the download link:
Posted by maxouthi on 1/20/2009 at 1:13 PM
One Suggestion...
In SQL Server 2000, I had the functionality to select all column headers in the results grid and autosize with a single click. In SQL Server 2005, I lost that functionality in the results grid and now have to single autosize the columns I need to view the text in.

Can we add the functionality back to the results grid. If we can, I can finally retire SQL Server 2000. Thx!
Posted by AaronBertrand on 12/16/2008 at 12:11 PM
Wow, give them time, they're not making a quarter pounder here. They've been saying Q4 for months, and guess what, it's still Q4. Anyway, it was released yesterday, if you hadn't already heard:
Posted by John Ray on 12/4/2008 at 2:16 PM
This thread has been running for 10 months and SP3 is still in CTP...WTF MS!!!!!
Posted by Nick Liles on 11/17/2008 at 7:25 AM
Absolutely SP3 for SQL is long overdue.
Posted by RandMan256 on 10/31/2008 at 12:48 PM
SQL Server 2005 SP3 Beta is available. The download is at
Posted by Daniel Iturriaga on 10/29/2008 at 6:07 AM
Helo, MS please! Put the battery with SP3!

I'm totally agree with NightOwlData.
Posted by Veener on 10/9/2008 at 5:20 AM
This is badly needed, I am deploying SQL Express SP2 on desktop PC's and there is a fix in one of the Cumulative Update packs that prevents a major part of our software from functioning.
Posted by xyvyx on 10/7/2008 at 12:23 PM
"... We will be able to get back to you in a few weeks with a formal statement regarding SP3.
Thanks, Matthias Berndt"

so it's been a few weeks, any statements?
Posted by Morris Lewis on 10/3/2008 at 2:08 PM
Here's what I wrote on the SQL Server forum. I updated it to 10/3/08:

For Vanderbilt University Medical Center, where I work, it can take years to move to a new version of a DBMS. It is October 3, 2008, and one of my main enterprise systems still runs SS2k. I have 15 applications using a server that hosts 80+ databases and close to 300 GB of data. I have another 13 migrated to SS2k5 and hope to have them all migrated by the end of Q1 2009. The main impediment to change is that our vendors have to certify each new environment to ensure it will not be detrimental to patient care or safety. If you have an application that pages doctors and nurses when a patient goes into cardiac arrest, it is an ethical, moral, and legal obligation to make sure changes to the systems that support that application work all the time. Bugs can quite easily cause death or serious medical issues in our environment, so we don't "fix" anything that isn't broken. When we do migrate, it is a year long process involving 100+ people doing everything they can to make sure patients leave our hospital in better health than they came in.

I would also like to add that my conservative approach has resulted in downtime being less than 5 minutes one server and less than 10 minutes on the other enterprise server. Those servers serve 2-3000 users every day, and are part of providing the care for about 1.2 million patients a year. Even small down times have a huge impact with those numbers.

So, Microsoft employees, think about your husbands, wives, children, mothers, fathers, sisters, brothers, and any other family member who has been in the hospital in the past, and realize that their health may have depended on your products working correctly 100% of the time when you decide that a new, untried application is better than an older, stable, trusted application or that untested cumulative updates are preferable to rigorously and publicly tested service packs.
Posted by archman_1 on 9/12/2008 at 12:11 PM
Our customers pay houndreds of thousands dollars for most expensive versions of SQL and they believe they have made the right choice. Don't let them (and us) down...
Posted by ChrisAVWood on 9/9/2008 at 9:41 AM
With another security problem in SQL2005 post SP2 coming out today that's included in a CU its more than about time that SP3 came out.

Posted by PDav on 8/21/2008 at 2:03 PM
My company is waiting for SP3.
Posted by LGee on 8/21/2008 at 1:02 PM
We really need SP3 Guys please hurry
Posted by adolf garlic on 8/21/2008 at 4:47 AM

                                                     Status update on this ?

Posted by cjmorgant1101 on 8/13/2008 at 10:55 AM
Please, please release SP3....
Posted by ChrisAVWood on 8/8/2008 at 7:09 AM
You must now have the time to bring out SP3 with SQL2008 available.

Posted by Bill Twomey on 7/25/2008 at 6:26 AM
Please convert the existing fixes into a service pack. My server needs one of the fixes, but I have to work around rather than install unsupported fixes. I want my SP3!
Posted by Shaun.Mitchell on 7/15/2008 at 9:37 AM
Please release SP3. We are up to CU 8 and I am being effected by a bug that CU 8 fixes but would rather wait for SP3 if I can
Posted by Daniel Smith on 7/13/2008 at 11:12 AM
Can't believe 6 people vote "No" for this. It's funny - if you look at the validation comments for the "no"s every single one that also left a comment appear to have voted wrongly by accident :-)
Posted by Angelo Hongens on 7/11/2008 at 7:17 AM
Pleeease create an SP3.. I'm still holding off a hotfix, because of company policy, and Microsoft warning 'only install if affected'. Well, we're affected (TOKENPERM_CACHE problems), but I'm still afraid to apply those on-demand hotfixes to our production machines.
Posted by Bob Fazio on 7/9/2008 at 7:26 AM
It's unfortunate that an issue with this much activity and validation hasn't been addressed yet.
Posted by ERPDBATOO on 7/8/2008 at 5:20 PM
SQL 2005's mainstream support ends on April 12, 2011, and I hope I'm not still running on a Post-SP2 cumulative hotfix at that date (though if it runs great I suppose I won't knock it either). But regardless, please continue to regularly provide service packs for SQL Server 2005. Microsoft's customers and business partners put great faith in Service Packs as quality-tested baseline fixes, and they view them as trusted, reliable prerequisites for successful product implementations.

As techs, I think politically hotfixes are an issue for many of us. I'd much rather tell a customer or a supervisor that I'm installing a "Service Pack" rather than a "hotfix" or a "cumulative hotfix." Its almost always harder to justify the risk incurred in fixing something that is inherently broken with a software patch than to propose instituting a change that will bring greater service from an existing technology investment. So keep those service packs coming! Thank you, T.Boda, MCSE
Posted by Sblackfo on 7/8/2008 at 12:28 PM
Create and Release SP3
Posted by DBA_PAL on 7/8/2008 at 6:00 AM
SP3 please.
Posted by Robert Russello on 6/23/2008 at 12:53 PM
Please release SQL Server 2005 SP3
Posted by ChrisAVWood on 6/17/2008 at 7:45 AM
CU8 is now out and the wording for some of the problems looks quite serious so a reliable, fully regression tested service pack is very much overdue. Both CU5 and CU7 contain comments about critical issues with Analysis Services so these CU's cannot be that well tested.

Posted by SQL_Guru on 6/11/2008 at 4:27 PM
Now it looks like they aren't sure if they will be releasing SP 3 at all. Now this just may be because the tech support people who work on connect don't know everything going on, but it still worries me.
"At this time, we don't know whether we have any plan to do SQL Server 2005 SP3." ... Posted by Microsoft on 6/11/2008 at 12:53 PM
Posted by Juliane Padrão on 6/4/2008 at 10:50 AM
Yes, please release SP3
Posted by LSC on 5/22/2008 at 7:22 AM
I can't believe it's gotten this bad at MS....we have to actually beg for a service pack to an enterprise database product in the middle of it's life-cycle. It shouldn't even be a question, yes there should be SP3 and probably SP4 before you discontinue mainstream support. When it comes time for renewal of everyone's EA contract and /or SA, you can bet this will be a point of conversation. All of this begs the question: Why upgrade to SQL2008 if we can't even get the service/support we need from SQL2005?
Posted by SP3SQL on 5/20/2008 at 12:09 AM
Posted by 5ilverFox on 5/13/2008 at 7:20 AM
Yes, please release SP3
Posted by Charles K. Kincaid on 5/12/2008 at 9:31 AM
If you are NOT going to release service packs for 2005 while it is in mainstream support and are only going to fix things in 2008 then the only right thing to do is provide FREE upgrades to 2008. If 2008 fixes so many things that are too hard to fix in 2005 then it seams that it would be cheaper for Microsoft to just upgrade people to 2008 and EOL everything else right now.
Posted by Jeff Agent on 5/12/2008 at 9:22 AM
I completely agree. Upgrading to a new version in an entrprise environment is no cakewalk. Even applying a service pack is not necessarily a no-brainer, but I would far rather apply SPs than upgrade the whole environment. Because of my many roles, it usually takes awhile to really get comfortable using all the changes effectively, especially with big new releases like 2005, only to have 2008 come out and be faced with yet more changes to learn/deal with.

But think about this... at least it isn't as bad as their forcing us to eventually migrate to Vista....
Posted by nbsMikeS on 5/12/2008 at 6:29 AM
Yes, release SP3
Posted by juniorguidugli on 4/22/2008 at 7:44 AM
I'm agree too. Release SP3 now!
Posted by fotis12 on 4/21/2008 at 1:32 AM
this is not an anoucment,

this is a joke made on the backs of thousands of developpers, DBAdmins, End Users and companies that have trusted sql server for production
Posted by Ickis99 on 4/16/2008 at 6:31 AM
"not too far away" of course ^^.
Posted by Ickis99 on 4/16/2008 at 6:29 AM
@dbrenn: Where it is? Not to fat away. Check this out:
Posted by dbrenn1 on 4/15/2008 at 12:10 PM
Now CU7 is out.

Where is SP3??
Posted by John Hardin on 4/9/2008 at 11:01 AM
Cumulative Updates are not a suitable long-term alternative to a fully tested and officially supported Service Pack for a core product like this, even though they may be acceptable for emergency repair of serious problems. Nor does the pending availablity of SQL Server 2008 excuse you from supporting the previous version properly.
Posted by John Homer on 4/9/2008 at 8:47 AM
I realize there is a huge expense associated with releasing an update of this magnitude. What Microsoft needs to understand is A) no one forced Bill and gang to start a software company, he could have made alarm clocks or something, and B) if something is worth doing, it's worth doing right. The point is, stop being cheap/lazy and do your job!
Posted by elionescu on 4/9/2008 at 1:02 AM
Maybe bad for business of sql2008 in short term, a sp3 for 2005 is good in the long term: proves that MS really cares about stability and, in fact, about customers.
Posted by Mike C_1 on 4/6/2008 at 9:27 PM
Where is the "formal statement" we were promised would be put forth in a couple of weeks (at the end of February)? Anyone have a link to it?
Posted by theBainster on 4/1/2008 at 5:47 AM
please release service pack 3; the current service pack 2 is way too confusing
Posted by Arnoud van Bers on 3/28/2008 at 5:51 AM
What is the status of SP3??
Posted by DB88 on 3/25/2008 at 5:26 AM
SP3 is way overdue.
I can not justify the risk installing this continued string of CUs
Microsoft, support your product!
Posted by dems01 on 3/12/2008 at 10:35 AM
Matthias, Matthias, Matthias... we are now 3 1/2 weeks from your last announcement... please where is the formal statement re SP3 that you promised us (as shown below)??? Have the SQLServer Community not yet provided you with enough votes or evidence that sp3 is desperately desperately needed?

Hello SQL Server community! Just wanted to let you know that your ask did not go unheard with the SQL Server development team. We do look at the highest voted suggestions on an ongoing basis. With SQL2008 coming to a close (don't miss the launch messages week after next together with WS08 and VS08!) we are actively planning our post 2008 projects. We will be able to get back to you in a few weeks with a formal statement regarding SP3.

Thanks, Matthias Berndt
SQL Server Release Services Posted by Matthias Berndt on 16/02/2008 at 09:04

/* --Please let us know that you are listening to us and respond to us - let us know how things are developing with SP3 */ !!!

Posted by Mikhael7 on 3/11/2008 at 3:24 PM
Yes, we need SP3.
Posted by Gillespie_D on 3/11/2008 at 9:18 AM
I agree - please create and release SP3
Posted by sqldraggon on 3/11/2008 at 7:29 AM
It’s a pain in the … having to apply each patch individually and wait and see if it causes any issues, then apply each patch to each of our Dev, QA, Stage and production servers. If the patch list is longer then a couple of pages … then it’s time for a Service Pack.

We want SP3 and we want it Now….
Posted by Keith Dorken on 3/11/2008 at 5:42 AM
As to waiting for SQL server 2008, we have customers who won't upgrade to our new product because it uses (requires) SQL server 2005; they are still using SQL server 2000 and won't/can't upgrade to 2005 because of their other applications.

So pushing all fixes into SQL server 2008 doesn't solve even our CURRENT customers problems (that ARE using SQL Server 2005) because they won't upgrade to 2008 just because we say so.
Posted by Keith Dorken on 3/11/2008 at 5:40 AM
As a development shop that has a product that USES SQL server 2005, it is important to OUR customers that this service pack is released. Nothing worse than determining that OUR product has a bug (as it appears to our customers) when the BUG is actually in SQL server 2005, and that Microsoft has a fix for it, but, by the way you have to ask Microsoft for it (and ignore their warning that it really shouldn't be applied). Our customers only blame us, not Microsoft, yet there is nothing we can do to solve their problem except point them at Microsoft.

Posted by Lee Everest on 3/7/2008 at 6:25 AM
Continued release of hotfixes signals more work to-do. Fix it now rather than pushing it off to SQL 2008 and making everyone fight through bugs.

Lee Everest
Posted by TomHamilton on 3/6/2008 at 8:55 AM
SQL Server is a flagship product. The security, performance and reliability reflect upon each of us and our applications, and in turn upon Microsoft. We need your best support and diligence that we as developers, DBA's and architects can promote and use this product. This is a very good release (2005) and as such will likely remain in use for several more years. Please help us continue to use this produict with peace of mind.
Posted by fpatou on 3/5/2008 at 1:59 PM
Please provide SP3!!!!
It's hard enough to install SQL SERVER Production Architectur with NLB and Cluster W32 and W64...then please simplyfy the mainteance of all of this with SP wich is more CUSTOMER oriented than CU....
Posted by Larry Charlton on 3/5/2008 at 11:33 AM
SP3 is a must for us. Since 2005 with bugs being regularly released with each Service Pack we just aren't bold enough to apply a CU to our production servers. Unfortunately the CU's contain fixes we need. Get a service pack tested and released and do it yesterday already!
Posted by Vincent Wylenzek on 3/4/2008 at 11:32 PM
Offcourse we need SP3, as long as SQL2k5 is supported, we'll need service packs. Additional updates aren't suitable to use and maintain.
Posted by jadebird on 3/4/2008 at 2:02 PM
Totally agree. We need the service pack 3 very much.
Posted by Diane Sithoo on 3/4/2008 at 1:33 PM
Yes, I have been victimized by trying to use the cumulative hotfix packages. On our clustered servers, with SP2 installed, which "supposedly" fixed the issue of having system dbs installed on a location other than "C:\Program Files\Microsoft SQL Server\..", we were unable to successfully apply any of the cumulative hotfix packages 1-3, resulting in "Database Services failed to install" messages. Now we are stuck, unable to rollback either. We have therefore stopped trying to install any further hotfixes as a result, but find we need the fixes that ar in cumulative hotfix 5. What are we to do then, just continue being ignored? That is not to mention the fiasco that was SP2's release in the first place, what with the different "versions" of SP2 out there. We need a stable SP3 please!!! At the very least, Microsoft should change their policy of supporting hotfixes (atleast the CUs), and provide free support for problems resulting from them!
Posted by rschurchill on 3/4/2008 at 6:16 AM
I understand why Microsoft may wish 2008 to pick up the shortcumming of 2005. However.....I'd like to see more of a commitment from MS in protecting their customers investment in software, particularly at this level.

They've made great advances in their community efforts over the past few years and it would go a long way with me if they were to show more faith with regards supporting products which are close to being superseded.
Posted by csoloway on 3/3/2008 at 1:00 PM
Any time you get over 3-4 updates for a service pack it makes life a lot easier to wait until the service pack that includes them all comes out. Lots of issues after sp2, so it's time.
Posted by Dan Guzman on 3/3/2008 at 5:03 AM
SQL 2005 SP3 should take priority over SQL 2008, at least in my opinion. I would of course prefer to have both but existing customers need SP3 desperately.
Posted by Microsoft on 2/27/2008 at 5:54 PM
Hello SQL Server community! Just wanted to let you know that your ask did not go unheard with the SQL Server development team. We do look at the highest voted community suggestions on an ongoing basis. With SQL2008 coming to a close we are actively planning our post SQL2008 projects. We will be able to get back to you in a few weeks with a formal statement regarding SP3.

Thanks, Matthias Berndt
SQL Server Release Services
Posted by Microsoft on 2/27/2008 at 5:26 PM
Hello SQL Server community! Just wanted to let you know that your ask did not go unheard with the SQL Server development team. We do look at the highest voted community suggestions on an ongoing basis. With SQL2008 coming to a close we are actively planning our post SQL2008 projects. We will be able to get back to you in a few weeks with a formal statement regarding SP3.

Thanks, Matthias Berndt
SQL Server Release Services
Posted by Greg Van Mullem on 2/27/2008 at 3:59 PM
It's definitely time for SP3. I got bit by one of these bugs a while back. It would have been nice if the bug had been fixed in a service pack before I suffered a week of intermittent outages. I never requested or applied the hot fix for the bug because I was able to recode a couple of stored procedures to fix the problem. MicroSoft should not use hot fix requests as their only metric for making a service pack because there are a lot of people who are coding around bugs instead of applying a scary hot fix.
Posted by ljian on 2/27/2008 at 1:11 PM
I agree and believe that this should be contingent on number/severity of bugs and not by popularity of the issue!
Posted by Daniel Mohr on 2/26/2008 at 6:06 AM
I agree with Hugo - it is high time for SP3 - At the time are to many hotfixes!
Posted by Sandeep Mishra on 2/25/2008 at 11:14 PM
Yes, I agree with above statement for Sql Server Service Pack 3,

It would help a lot for Database Development.


Posted by tcmdba on 2/25/2008 at 11:14 AM
I totally agree we need SP3 and maybe a SP4 one day. It may be quite some time before SS2008 is released and is stable. And we typically do not install a major SQL Server release until at least 1 SP has been released.
Posted by bitbucket2 on 2/25/2008 at 10:16 AM
Agree with Hugo ... this product is still supported, so Microsoft SUPPORT IT PROPERLY !!!
Posted by Ricardo Vergel on 2/25/2008 at 6:46 AM
I totally agree. MS must release SP3.
Posted by Marcelo Andretto on 2/25/2008 at 5:17 AM
Last SP2 was create 2007/03/01. Microsoft create two SP by year. Now who will create SP3 after one year last SP2.
Marcelo Andretto
Posted by Olaf Pietsch DETECON on 2/25/2008 at 1:47 AM
We use serveral SQL Server 2005. We are not able to test and install each Hotfix/Update. I think SQL Server 2005 will be essential for several years. (It is a experience from SQL Server 2000.) Becaues of this I suggest and I aks for a SP3 for SQL Server 2005.

SQL Server 2008 do not help us in this, because the applications need serveral time to be SQL Server 2008 aware.
Posted by Nilton Pinheiro - MVP on 2/22/2008 at 7:48 PM
With CU6 I think that is time to make a SP3!
Posted by 1_1 on 2/22/2008 at 4:18 PM
properly fix your bugs - whats the holdup? and you then wonder why ms gets a bad wrap
Posted by tosscrosby1 on 2/22/2008 at 1:21 PM
Unless an "urgent" hot-fix, I'd rather bring my server down once for a service pack than numerous times for all the patches. Please SP3 me!!!
Posted by Hugo Kornelis on 2/22/2008 at 8:50 AM
Since Cumulative Update 6 is now out as well, and includes some important fixes, I have edited the description and proposed solution to include the sixth CU.
Posted by antzz1 on 2/21/2008 at 3:24 PM
SQL Server 2005 is one the best DBMS platforms around. SP3 will make it even better!!!    Just a suggestion, why not make SP3 mandatory in order to upgrade to 2008?
Posted by ChrisAVWood on 2/21/2008 at 9:38 AM
More reason to bring out SP3. The KB for CU5 has just been changed and includes a Crtical reference if you are using Analysis Services. The resolution is to use CU6.

Posted by ib64 on 2/21/2008 at 9:15 AM
The SP3 is long over due and must be released as soon as possible.
Posted by MegaSQLBI on 2/20/2008 at 11:49 PM
Yes, we need SP3
Posted by fnieto on 2/20/2008 at 11:14 PM
please, a SP3 for SQL 2005
Posted by Dan English on 2/20/2008 at 7:46 PM
I definitely agree. This is long over due and I believe it has been at least a year from when SP2 was released. These should be coming out at least on a yearly basis if not every 6 months to keep the software patched for known bugs. Some users might not even know they are experiencing some of the issues or that there are fixes that they should have in place.
Posted by wpwood on 2/20/2008 at 7:06 AM
How many times may I vote? I am from Chicago after all.
Posted by MysteRAE on 2/20/2008 at 7:04 AM
We invest in SQL, gives us the support we need, release SP3 and any additional releases required until the product is no longer supported
Posted by C_S Solutions, Inc,_ on 2/20/2008 at 7:00 AM
This should be a no-brainer. Why is it even up for vote?
Posted by Greg E on 2/20/2008 at 6:29 AM
The partial 'cumulative update' adds a layer of confusion. They aren't well publicized - not like SP's usually are. You have to first find them (thanks to some for keeping lists), then request them.

Although SQL 2008 is close to release, even after release it will likely be 6 months to a year before upgrading. So a Microsoft Release is not an automatic upgrade.
Greg E
Posted by Damon T Wilson on 2/20/2008 at 5:32 AM
SQL Server 2005 SP3 is overdue for such a heavily used product.
Posted by AVerzijl on 2/20/2008 at 4:35 AM
Each of our client's businesses depend on the reliability of the underlying database. For each of our clients the investment in a new version of SQLServer is significant. We release one major and one minor service pack each year for our own solutions. One would expect that Microsoft would extend the same commitment to its customers. The last SP for 2005 is one year ago, this is not a good reflection of MS' commitment to its corporate customers.
Posted by MRR - Tst on 2/20/2008 at 4:21 AM
I agree with Hugo, too - it is time for SP3.
Posted by davide_c on 2/20/2008 at 3:32 AM
Have you tried installing a fresh Windows XP SP2? Try. Then connect to windows update. You will have to download 60-70 fixes, then download IE7, then the patches to IE7, ...

SQL 2005 SP3 is needed; if they follow the XP SP3 path, it's going to be a looong wait...
Posted by Randy in Marin on 2/19/2008 at 9:35 AM
Please include cumulative package 6 in SP3. However, I'd rather apply a "cumulative package 1" to SP3 if given no other choice.
Posted by KBLando on 2/19/2008 at 7:17 AM
Yes, I totally agree that Service Packs are necessary and SP3 for SQL2K5 is due. Please roll these up into a service pack that has had full testing. There are quite a few in here that are important (especially the performance ones).
Posted by Todd Carrier on 2/18/2008 at 4:09 PM
Please continue to release service packs in a consistent manner. Our Envirionment has too many SQL Servers to manage different versions / cumulative updates. Please release SQL 2005 sp3 and a final SQL 2000 sp5 service pack, if fixes have been addressed
Posted by Simon Doubt on 2/18/2008 at 2:58 PM
Yes... SP3 is a good idea.
Posted by danschl on 2/18/2008 at 1:05 PM
what better way can microsoft push everybody to 2k8 if they dont fix 2k5

If 2k5 is stable then dba's will wait at least a year maybe more before pushing 2k8
Posted by jamome2 on 2/18/2008 at 9:43 AM
Come on SQL Server team, where is SP3? I vote for quality (Performance & Reliability) over new features any day!
Posted by greg grow on 2/18/2008 at 7:55 AM
I would like to see SP3. For example: Mirroring wasn't official till SP2 and in my opinion, the technology around Mirroring is still RTM. I would like to another release of a service pack. I would rather apply a SP than keep running these hotfixes. Please send us the SP3 upgrade.
Posted by shummel on 2/18/2008 at 6:49 AM
I agree that SP3 is necessary and SP4 and X should be scheduled for the life of SQL2K5.
Posted by wpwood on 2/18/2008 at 6:40 AM
I thought that is what 2008 is! Now if everyone goes out and buys vista then MS won't need the revenue stream from the 2008 upgrades. Perhaps then they would continue to support 2005. Of course they should provide SPs up until the end of the product life cycle.
Posted by ALZDBA on 2/18/2008 at 4:06 AM
Cut the Cumulative Hotfixes...... We need a Servicepack !


Why, because IMHO a SP is considered to be a stable release, tested well by the manufacturer. Certainly worth a general test and go.

A cumulative update is just a new package of hotfixes, designed for certain issues, so IMO not _that_ stable for us (systems managers) to give it a general test and go.

Also with CUs the frequency is to high to set up a release cycle every time.

After all, we have to determine which version of the software we will install by default when a new instance is being asked for.
For now that is set to SQL2005 SP2 + CU4.
But the active production instances are not yet being upgraded with CU4. (they are still on CU2)
Posted by The Data Man on 2/18/2008 at 1:07 AM
Please, bring SP3 on!
Let's keep SQL Server the best database platform and stay proactive.
Prevention is better than a cure!

Phillip Cox
Posted by Matthias Berndt [MSFT] on 2/16/2008 at 9:04 AM
Hello SQL Server community! Just wanted to let you know that your ask did not go unheard with the SQL Server development team. We do look at the highest voted suggestions on an ongoing basis. With SQL2008 coming to a close (don't miss the launch messages week after next together with WS08 and VS08!) we are actively planning our post 2008 projects. We will be able to get back to you in a few weeks with a formal statement regarding SP3.

Thanks, Matthias Berndt
SQL Server Release Services
Posted by Adam Bean on 2/15/2008 at 12:07 PM
Typical Microsoft ... they'll never release SP3. Instead they'll state that all the shortcomings and problems of 2005 will be resolved in 2008. They're up to 6 cumulative updates now, which have addressed an arsenal of known problems, yet you can't obtain them unless you experience the problem and call them to report it. So they'd rather let you experience said problems, which could and does happen in a production environment, than to be preventative and resolve the issues before they become apparent. Good call Microsoft, keep up the good work.
Posted by Tom Moreau on 2/15/2008 at 8:11 AM
Posted by testst on 2/14/2008 at 12:36 AM
I can't believe my eyes. It should be obvious that SP3 is needed!
Posted by David Beavonn on 2/13/2008 at 3:00 PM
If they were important enough for you to fix (in spite of the upcoming release of SQL 2008) then they are important enough for us to install. I'd rather not risk the hours and days we may spend troubleshooting new issues if they can be fixed proactively.
Posted by DB88 on 2/13/2008 at 1:30 PM
I also agree that SP3 is overdue. Follow the timeline so far:

11-7-2005 RTM
4-19-2006 SP1 ( 5 months )
2-20-2007 SP2 ( 10 months )

? SP3 12 months and counting...
Posted by contec on 2/13/2008 at 9:21 AM
absolutely agree! release sp3!
Posted by el-tigre on 2/12/2008 at 5:52 AM
Service pack 3 should be released!
Posted by FrankRe on 2/12/2008 at 5:46 AM
Unsupported bugfixes sounds to much like Oracle, please bring out supported bugfixes or a SP3.
Posted by fotis12 on 2/12/2008 at 3:36 AM
sql server 2005 is like the product is entirely re-written, full of bugs
we had many issues on a very serious production enviroment, when we moved from 2000 to 2005, 2005 was already in sp2 and yet, full of very serious bugs.
microsoft support policy to break down in single support issues, is not helping us at all
there is no way im gonna trust any product again before it reaches sp3
or better, if ms doesnt want to help regarding the support level we have, completely abandon it.
Posted by Plamen Ratchev on 2/10/2008 at 7:54 PM
I agree, SP3 is long time overdue.
Posted by Glenn A. Berry on 2/7/2008 at 8:46 AM
I agree that it is time for SP3 for SQL Server 2005. CU6 for SP2 will be out soon. Since service packs get even more testing than cumulative updates, Microsoft should release a SP3 sometime soon (definitely before 2008 RTMs).

Glenn Berry, SQL Server MVP
Posted by ChrisAVWood on 2/7/2008 at 6:21 AM
Seems SP3 is coming based on a comment in bug 264653 dated Jan 31st 2008.

Posted by B988B731-4D34-4DC4-8F7B-645C57859E61 on 2/6/2008 at 3:11 PM
Many users are just NOW moving up to 2005 because they've been waiting for a few service packs for it to stabilize. They aren't even going to consider going to 2008 in a production environment until it has at least 1 or 2 service packs available. I'm guessing that's a good year out. Right now, if MS wants to encourage users to move up to the latest version, that can only be 2005. Given that, MS should be doing everything in their power to provide the best possible release of 2005 for them to move to. Leaving so many bugs "officially" unfixed is completely unacceptable.
Posted by GregGalloway on 2/6/2008 at 9:19 AM
Agreed that we need MS to go through the regression testing level that we've come to expect for service packs and come out with SP3. Most organizations aren't wild about installing hotfixes.

Don't let SQL2005 SP3 slow down SQL2008 enhancements.
Posted by Bryan S on 2/5/2008 at 4:56 PM
From CU1 to CU5 over 250 bugs have been fixed. I cannot imagine that this is not enough bugs to do further testing and roll out SP3 for SQL Server 2005.

Please roll these up into a service pack that has had full testing. There are quite a few in here that are important (especially the performance ones).
Posted by PhilMo on 2/4/2008 at 1:25 PM
2008 is released so soon after 2005 and now Microsoft wants to hold back on service packs for 2005. What is happening to 2005 and why did my company invest in the 2005 product?    Microsoft's customer base has diligently followed the path to sql 2005, now it's time for Microsoft to show a commitment. Service pack 3 is long overdue.
Posted by PoorKarl on 2/4/2008 at 4:32 AM
Please, please, please give us SP3.
Posted by Belthazor78 on 2/4/2008 at 1:18 AM
I'm agree too. Release SP3!
Posted by Romelard Fabrice MVP on 2/2/2008 at 7:27 PM
I'm agree to.
To many upgrade patches complexe to manage in production or test farm
SQL Server MVP and SharePoint admin
Romelard Fabrice
Posted by AKuz on 2/2/2008 at 1:03 PM
I agree with Hugo - it is high time for SP3.
Alex Kuznetsov, SQL Server MVP
Posted by AshishGupta on 2/1/2008 at 4:59 PM
I understand the importance of getting a new product version (SQL 2008) out the door, but it should not come at a cost of diminished support levels and policies on existing "supported versions".
Posted by paschott on 2/1/2008 at 1:28 PM
I can't install the last cumulative update on my local machine. It unpacks the files, runs through the process, then gives a non-descript error and exits leaving no trace of the log files to diagnose the cause of the error. Having a formally released SP would be nice. Also agree that telling people to wait for the next SP instead of requesting a CU package then saying there will be no SP because nobody's asking for it seems to be a wierd way to determine whether to release or not.
Posted by WChaster on 2/1/2008 at 1:06 PM
Is there not a formula for determining this?
X number of hot fixes AND/OR security updates OR number of month since last SP ...
Posted by suzar on 2/1/2008 at 12:50 PM
Yes, I totally agree that Service Packs are necessary and SP3 for SQL2K5 is due.
Posted by way0utwest on 2/1/2008 at 12:38 PM
Build, test, and release SP3. Plan on SP4 and 5 as well until this version is no longer supported.
Posted by Cory E on 2/1/2008 at 12:33 PM
yes - Create and release SP3.
Posted by SQL_Menace on 2/1/2008 at 12:26 PM
I totally agree with Hugo