Log in
::
Register
::
Not logged in
Search:
Home
Articles
Editorials
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Advertise
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Administering
»
DAC issue
22 posts, Page 3 of 3
««
«
1
2
3
DAC issue
Rate Topic
Display Mode
Topic Options
Author
Message
ALZDBA
ALZDBA
Posted Monday, July 06, 2009 7:31 AM
SSCarpal 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
sudhakara
sudhakara
Posted Monday, July 06, 2009 10:55 AM
Old 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 »
22 posts, Page 3 of 3
««
«
1
2
3
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2009 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use