February 1, 2008 at 9:57 am
Service Packs=Yes
Even though I will implement the weekly fixes and mostly without testing, as there is never enough time or resources. We have grown comfortable with our DR methods to make this acceptable.
It seems, though, when you have to recreate a new instance or rebuild an current one that the time involve adding all those incremental fixes; makes the process drag on forever, this is when the SP would be great.
What is in a End of Life Service Pack (SP)
When any software company ends the support life for a product the they still have a client base using, I would like to see them create a final SP that rolls up all previous release patches, hot fixes et la, but what benefit would this give the SW company. The benefit would be for the client and that may delay them moving to the new version and delay the repurchase of the application.
😀
ACN is the world's largest direct seller of telecommunications and essential services.
http://helpu.acndirect.com/
ACN Digital Phone Service customers automatically enjoy unlimited calling to 60 landline
destinations around the world, including India, Mexico and the UK!
:hehe:
February 1, 2008 at 10:05 am
We are supporting both 2000 and 2005 in production. It would be nice to have a sp5 to wrap 2000 up before support closes. And 2005 sp3 should be automatic. We would like to see it.
Not all gray hairs are Dinosaurs!
February 1, 2008 at 10:16 am
Judging by previous replies I will be controversial and say NO to SQL 2000 SP5. I think it is widely accepted that 8.00.2187 is the roll up to go to for 2000 and that is stable. If an SP5 is bought out the powers that be will expect it to be applied, which will mean downtime and place the installations at risk, because lets face it risk is introduced when you upgrade. I am not suffering from any problems on my 2000 servers so I don't want to apply a roll up of fixes to problems I have not got.
As for SQL 2005 SP3 though....definitely YES. As the CU patches say in the notes, only apply these fixes if you are suffering from the problems addressed, which makes me nervous I am applying untested fixes to production boxes that could come back and bite me, but I know I cannot just leave the box at SP2 because that has known bugs. It goes completely against what I have learnt over the years, which is to apply security patches and service packs, but only apply hotfixes if I hit the problem.
I do wonder sometimes how much experience the MS guys have of looking after live systems, where we cannot take them down on a whim to fix problems.
On my soapbox I am sure I heard in the very early days of 2005 that backing out service packs would be a lot easier, not requiring a full uninstall\reinstall, but that does not seem to have materialized. These issues would be so less important if it was easier to back them out. Every upgrade is a heart in the mouth moment.!
---------------------------------------------------------------------
February 1, 2008 at 10:20 am
Yeah, I'd sure love a SP3...then maybe in a few months an SP4 for the SP3; maybe by the time SQL 2008 comes out we could be up to SP5. What happened to the regularly releasing SPs anyways? Was that just a rumor?
I find it hard to believe that MSFT doesn't have enough requests for an SP3 for SQL 2005. I can understand that maybe some people haven't requested because of the whole SQL 2008 coming in March 2008...now that that's been clarified as to wait an additional 6 months longer...why wouldn't we start asking for SP3 then? I don't know about you, but I don't want to keep waiting for them to put out SQL 2008 and ignore the problems with SQL 2005 (sometimes feel like the red-headed stepchild because I upgraded to SQL 2005....mommy...daddy...can you help me out here??)
Happy Friday everyone!!!
~ Without obstacles, you cannot progress ~
http://sqln.blogspot.com/
February 1, 2008 at 10:46 am
george sibbald (2/1/2008)
Judging by previous replies I will be controversial and say NO to SQL 2000 SP5. I think it is widely accepted that 8.00.2187 is the roll up to go to for 2000 and that is stable.
We upgraded to SP4 last fall which put us on 8.00.2040. What makes up 8.00.2187? I'm a new DBA that inherited some systems and this is the first hint I've heard that we may not be completely up to date.
February 1, 2008 at 10:57 am
pauls2
see http://support.microsoft.com/kb/916287
---------------------------------------------------------------------
February 1, 2008 at 12:05 pm
An unpatched 2000 SP4 is not a good place to be, especially if you are using AWE. There were some significant fixes posted to that subsystem, to the optimzer, etc after the SP4 release.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
February 1, 2008 at 12:06 pm
it's a rollup update following SP4 meaning that you need SP4 installed before installing it.
February 1, 2008 at 1:28 pm
Hi Steve,
I see that you have beaten me to the punch. That's the down side of having something else as your day job 🙂
Anyway, I still have decided to blog about this (see http://sqlblog.com/blogs/hugo_kornelis/archive/2008/02/01/want-a-service-pack-ask-for-it.aspx, and I have also filed a suggestion to release service pack 3 on connect (see -and vote!- https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=326575).
Let's hope that the huge amount of support here will be extended by a huge amount of votes on connect. Maybe that can convince Microsoft that they should release a service pack!
February 1, 2008 at 1:39 pm
:), Hugo, it's not often I'd beat you to anything.
I've voted on Connect and please feel free everyone to add a vote (mark the stars in the upper left) and a comment.
February 1, 2008 at 3:13 pm
Yes. Most definitely I want a SP3. It is very confusing to keep track of all the roll-ups and patches. I thought the MS advice on the subject was unless you specifically need the patch to correct some known issue (unless it's security related) wait on the SP. So have they changed this advice? Install all patches? I have a couple issues going on right now that I have been waiting on a SP to correct and just using a work around for now. Some of the warnings on the patches make you nervous about installing them if you have a relatively acceptable work-around.
Also, note that when using purchased software, often vendors will test to a SP level. Without SP to set a line in sand, I can see the conversations back and forth to vendors when problem arise, " I've got patch a,b, f, and k, what patches have you tested with. It's just not a good scenario. So you install only CRITICAL patches, wait on SP and install a SP when a vendor says they have tested.
February 2, 2008 at 8:23 am
The latest post-SQL-2000-SP4 rollup, version 8.0.2187, has a lot of the fixes required, including a fix for the AWE bug.
Microsoft has extended support for SQL 2000 SP4 to 2013, although that is not extended support, ie. no new hotfixes will be produced.
Where I work, we have been upgrading all our SQL 2000 instances to version 8.0.2187, as was suggested to us by MS Support.
There is one issue we have encountered with this version. It is regarding queries involving the numeric data type, and we have had to enable flag 9059 as a startup parameter to revert back to pre-sp4 behavior. Pls see this link for more info on this:
FIX: A query that involves data that is the numeric data type may return incorrect results in SQL Server 2000 SP3 and in earlier SQL Server 2000 service packs:
http://support.microsoft.com/kb/899976
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
February 15, 2008 at 2:23 am
It might make them see sense...but we need enough votes...!!!
(http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=326575)
Oraculum
February 19, 2008 at 3:43 am
An update from MS......
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
Oraculum
February 19, 2008 at 7:34 am
Matthias,
Thanks for the note and listening to us.
Steve
Viewing 15 posts - 46 through 60 (of 72 total)
You must be logged in to reply to this topic. Login to reply