SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
Search:  
 
 
        
Home       Members    Calendar    Who's On


«««123

DAC issue Expand / Collapse
Author
Message
Posted Monday, July 06, 2009 7:31 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 4:47 AM
Points: 4,752, Visits: 3,529
Just another thought: You are at the console, or are using a remote desktop solution to run SAC, right ?


We now only have SP3 instances with sql2005 and are not experiencing the problem you state.

How To apply SP3:
www.sqlservercentral.com/articles/Installation/66128/

Play it safe: start with a full backup of your instance(s)


fyi:
We didn't encounter problems when upgrading from sp2 cu2 to SP3 on our 2-node sql-cluster (multiple instances).
We do pay attention for the cluster resource to reside on the same node as the sql instance to be upgraded.
We even upgraded multiple instances in a single run. We moved all instances to the same node before starting the upgrade.

Off course it will not hurt to have a spare/backup set of resource db files !
We take a copy of them after every upgrade (because at that moment is planned downtime).

One thing we did observer is the needed reboot after the first instance + the client software have been upgraded.


Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere

Very usefull HowTo for forums:
- How to post Performance Problems
- How to post data/code to get the best help
Post #747713
Posted Monday, July 06, 2009 10:55 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, October 27, 2009 10:33 PM
Points: 330, Visits: 444
ALZDBA (7/6/2009)
Just another thought: You are at the console, or are using a remote desktop solution to run SAC, right ?





We now only have SP3 instances with sql2005 and are not experiencing the problem you state.

How To apply SP3:
www.sqlservercentral.com/articles/Installation/66128/

Play it safe: start with a full backup of your instance(s)


fyi:
We didn't encounter problems when upgrading from sp2 cu2 to SP3 on our 2-node sql-cluster (multiple instances).
We do pay attention for the cluster resource to reside on the same node as the sql instance to be upgraded.
We even upgraded multiple instances in a single run. We moved all instances to the same node before starting the upgrade.

Off course it will not hurt to have a spare/backup set of resource db files !
We take a copy of them after every upgrade (because at that moment is planned downtime).

One thing we did observer is the needed reboot after the first instance + the client software have been upgraded.


Yes .. i have took the virutal machine by mstsc console and trying to modify the SAC ...


thks for your information ....
Post #747892
« Prev Topic | Next Topic »

«««123

Permissions Expand / Collapse