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

Apply service pack Expand / Collapse
Author
Message
Posted Thursday, August 7, 2014 4:02 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Wednesday, December 10, 2014 10:06 AM
Points: 1,792, Visits: 3,261
I usually apply the service pack in our maintenance window.

But just curious, can I install service pack to SQL when people are on line?

we don't have many people using the server now, but maybe a couple of them.
Just curious, for I never did so.

thanks
Post #1600925
Posted Friday, August 8, 2014 8:32 AM


UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: 2 days ago @ 2:44 PM
Points: 1,494, Visits: 2,809
You will have downtime when applying a service pack.

Bob
-----------------------------------------------------------------------------
How to post to get the best help
Post #1601208
Posted Friday, August 8, 2014 9:45 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Wednesday, December 10, 2014 10:06 AM
Points: 1,792, Visits: 3,261
Thanks, realized it when I tried to do.

Another question, if we don't need the feature of the service pack, is it necessary to do service pack?

I found in all cases doing the service pack or not does not make any difference to our applications.

So should we do each service pack, or follow the rule that if we need the new feature then apply it, otherwise stay at the version when we installed them.

Thanks
Post #1601243
Posted Friday, August 8, 2014 9:49 AM This worked for the OP Answer marked as solution


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 9:34 AM
Points: 5,480, Visits: 10,303
Two good reasons to apply service packs, even if you don't think you need them:
(1) They contain patches for security vulnerabilities
(2) When the product goes into extended support, Microsoft will only help you if you have the last service pack applied

John
Post #1601246
Posted Friday, August 8, 2014 12:54 PM This worked for the OP Answer marked as solution
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 8:01 AM
Points: 416, Visits: 1,345
sqlfriends (8/8/2014)
Thanks, realized it when I tried to do.

Another question, if we don't need the feature of the service pack, is it necessary to do service pack?

I found in all cases doing the service pack or not does not make any difference to our applications.

So should we do each service pack, or follow the rule that if we need the new feature then apply it, otherwise stay at the version when we installed them.

Thanks


John pretty much answered your question.

My only suggestion would be, do not jump from your seat and apply service packs if they just came out. Even though they are extensively tested by Microsoft, issues may arise. Most recent one is/was with SQL 2012 SP2 and possible data corruption when doing online ReIndex on Ent. edition. A hotfix was provided few days after that.

By the way, I recently applied SQL2012 SP2 on one of my boxes and had no problems at all. I applied and tested the application on a test server though, but the process went smoothly on production and test box.

Just dropping my 2 cents.
Post #1601313
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse