Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12345»»»

Regular Service Expand / Collapse
Author
Message
Posted Tuesday, April 27, 2010 9:12 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 4:38 PM
Points: 31,018, Visits: 15,453
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
Post #911597
Posted Wednesday, April 28, 2010 1:01 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 2:20 PM
Points: 2,136, Visits: 870
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
Post #911656
Posted Wednesday, April 28, 2010 1:11 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, September 18, 2014 1:36 PM
Points: 6,002, Visits: 8,267
Hi Steve,

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

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
Post #911661
Posted Wednesday, April 28, 2010 1:20 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, September 18, 2014 11:12 AM
Points: 212, Visits: 1,116
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.
Post #911664
Posted Wednesday, April 28, 2010 3:21 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, May 7, 2014 5:23 AM
Points: 197, Visits: 152
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.


Post #911722
Posted Wednesday, April 28, 2010 4:46 AM


Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, December 19, 2013 2:03 PM
Points: 62, Visits: 379
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.
Post #911772
Posted Wednesday, April 28, 2010 5:07 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, September 8, 2013 5:39 PM
Points: 263, 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
Post #911780
Posted Wednesday, April 28, 2010 6:06 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: 2 days ago @ 1:34 PM
Points: 1,276, Visits: 2,803
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.



Post #911824
Posted Wednesday, April 28, 2010 6:20 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 9:22 AM
Points: 2,593, Visits: 2,225
I vote for the SP's on a regular basis. I like to avoid the Cu's unless it fixes a problem.

Mike

The more you know, the more you know you don't know.

_____________________________________________________________________________

A word to the wise ain't necessary, it's the stupid ones who need the advice ...Bill Cosby
Post #911840
Posted Wednesday, April 28, 2010 6:28 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, July 17, 2013 12:22 PM
Points: 107, 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.
Post #911846
« Prev Topic | Next Topic »

Add to briefcase 12345»»»

Permissions Expand / Collapse