SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Regular Service


Regular Service

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)SSC Guru (63K reputation)

Group: Administrators
Points: 63342 Visits: 19115
Comments posted to this topic are about the item Regular Service

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
David Conn
David Conn
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3149 Visits: 1148
So far I've found SQL Server 2008 SP1 to be rock solid. I run the X64 version on a Windows Server 2008 x64.

I'm now contemplating R2 i.e. not worried about SP2.

My company is likely to adopt Power Pivot so we need R2 and Office 2010.

It is nice to be bleeding edge for a change but with 2008 I have nothing bad to say about it, only praise.

David
Hugo Kornelis
Hugo Kornelis
SSChampion
SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)

Group: General Forum Members
Points: 11088 Visits: 12001
Hi Steve,

I'm sure you won't be surprised a bit about my comments :-D

it is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems.

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.

These are two quotes from this KB article on CU8 for SQL2005 SP2. All other CUs I checked have, and always had, the same or similar advice. Many companies will take this advice seriously, so until they run into real problems, they will avoid the CUs and wait for the next SP.

Another problem I have with the "no SPs" policy is that this text above is, maybe not explicit, but at least implictly a promise that there will be a next service pack. How can you tell customers to wait for a next service pack, than not release one?

So yes, I do think that service packs should be released, and on a regular and predictable cycle. The first one 6 months after RTM, and then a 12-month cycle. Unless really serious or annying bugs are fixed, that should warrant an intermediate extra SP (or, better, a CU with a different advice).

Either that, or increase the testing of CUs, advice customers to install each CU, and abandon SPs completely.


Hugo Kornelis, SQL Server MVP
Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
Abrar Ahmad_
Abrar Ahmad_
SSC-Addicted
SSC-Addicted (454 reputation)SSC-Addicted (454 reputation)SSC-Addicted (454 reputation)SSC-Addicted (454 reputation)SSC-Addicted (454 reputation)SSC-Addicted (454 reputation)SSC-Addicted (454 reputation)SSC-Addicted (454 reputation)

Group: General Forum Members
Points: 454 Visits: 1296
David Conn (4/28/2010)


It is nice to be bleeding edge for a change but with 2008 I have nothing bad to say about it, only praise.

David


Please add 1 more vote to it. If not biased about Oracle etc Releases.
athurgar
athurgar
SSC Veteran
SSC Veteran (249 reputation)SSC Veteran (249 reputation)SSC Veteran (249 reputation)SSC Veteran (249 reputation)SSC Veteran (249 reputation)SSC Veteran (249 reputation)SSC Veteran (249 reputation)SSC Veteran (249 reputation)

Group: General Forum Members
Points: 249 Visits: 162
I agree with Steve, a regular Service Pack, every year for the supported life of the product. That would mean Service Pack 4 is that last for SQL Server 2008. You can live with that, without getting to SP5a (remember SQL 6.5). It also gives you an upgrade schedule and some known certainty, without having to lobby for a service pack (SQL 2005). The wider implication would be not just for SQL Server but for every Microsoft supported product.



John Magnabosco
John Magnabosco
SSC-Enthusiastic
SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)SSC-Enthusiastic (171 reputation)

Group: General Forum Members
Points: 171 Visits: 385
I am with you, Steve. There are always security vulnerabilities to mitigate and features to tweak. SPs could also be used to stair step the product into the next major release.
James Stover
James Stover
Old Hand
Old Hand (385 reputation)Old Hand (385 reputation)Old Hand (385 reputation)Old Hand (385 reputation)Old Hand (385 reputation)Old Hand (385 reputation)Old Hand (385 reputation)Old Hand (385 reputation)

Group: General Forum Members
Points: 385 Visits: 862
Releasing CU's and SP's must be incredibly expensive and laborious for MS. And yet, they are freely available to anyone - even those who DON'T own the product. And yet, here we are complaining that we aren't getting our FREE update.

I don't know about you, but I have to pay good money (usually about $350) for regular servicing on my car. Trust me, I would wait an extra month or two or six if I could get it for FREE.


James Stover, McDBA

Markus
Markus
Hall of Fame
Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)

Group: General Forum Members
Points: 3023 Visits: 3770
I guess I am confused by all of this from Microsoft. CU's originally were supposed to ONLY be applied if you were experiencing a problem that was addressed by a CU as CU's originally had a disclaimer stating that fixes within these were to undergo more testing to be rolled up into a SP. However, it almost appears that CU's are now patches to be applied instead of a rolled up SP anymore. The last time I opened a case with Microsoft on a SQL 2008 issue the technician suggested applying the latest CU eventhough it had nothing to do with my issue.

I wish Microsoft would at least officially state one way or another what CU's intention is and if and when we will get a SP4 for SQL 2005 or a SP2 for SQL 2008.



mbricker-600840
mbricker-600840
Hall of Fame
Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)

Group: General Forum Members
Points: 3579 Visits: 2410
I vote for the SP's on a regular basis. I like to avoid the Cu's unless it fixes a problem.

Mike

“I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant.”...Robert McCloskey

___________________________________________________________________
bwillsie-842793
bwillsie-842793
SSC-Enthusiastic
SSC-Enthusiastic (155 reputation)SSC-Enthusiastic (155 reputation)SSC-Enthusiastic (155 reputation)SSC-Enthusiastic (155 reputation)SSC-Enthusiastic (155 reputation)SSC-Enthusiastic (155 reputation)SSC-Enthusiastic (155 reputation)SSC-Enthusiastic (155 reputation)

Group: General Forum Members
Points: 155 Visits: 290
I vote for SP's on a regular basis. My gut instincts tell me that cherry picking CUs is going to cause me problems at some point.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search