January 14, 2009 at 8:37 am
Hi,
We have active/passive clustered environment in production. Sql Server is in 2000 verison. Cluster is working fine. We are going to upgrade sql server 2000 to sql server 2005. We don't have possiblility to test cluster upgrade in development environment to practice. Unfortunately we have to do directly in production. Can anyone please advise proper steps to follow in this sql upgrade in clustered environment. I am looking at many articles on BOL but I want to hear from real experience and any suggestions so this upgrade goes smoothly.
Thanks
January 14, 2009 at 10:15 am
My advice would be to go for a Windows 2003 Cluster, which is more stable and easy to install. What are your options- Inplace upgrade or side by side?
Thanks!!
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 14, 2009 at 10:34 am
I would suggest you to go for side by side upgrade incase something happens its easy to revert back that way.
If everything goes well inplace is the easiest one.
Why dont you guys go for 2008 instead of 2005. Cluster in 2008 will have less issues than 2005.
January 14, 2009 at 1:59 pm
We have decided to go for inplace upgrade.Since we don't have enough place for side by side.we have a vendor application on this server it supports only sql 2005, so we are upgrading to sql server 2005 only.
January 14, 2009 at 2:47 pm
Mahi (1/14/2009)
We have decided to go for inplace upgrade.Since we don't have enough place for side by side.we have a vendor application on this server it supports only sql 2005, so we are upgrading to sql server 2005 only.
Keep in mind, at DRP time, because you've chosen an in place upgrade, you'll have to follow the same path during your re-install to get to the point where you can restore your db !
(i.e. first install sql2000, upgrade to sp4, then upgrade to SQL2005, apply the current SP (or the one you need), restore your system and user databases)
This all to get your registry and (file) security back in place !
And the one thing you don't have at DRP-time, is Time itself !
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 15, 2009 at 1:40 pm
I was thinking if anything goes wrong with Inplace upgrade , I have to just uninstall 2000 and install 2005 should be suffice. Do I really need to install 2000 apply sp4 and then upgrade to sql 2005.
January 16, 2009 at 12:14 am
an in place upgrade inherits some settings from sql2000. The goal (from ms) is to keep it working !
With a fresh install of sql2005, it will implement best practises and some "features" will be shut off. (e.g. cmdshell)
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 16, 2009 at 9:16 am
First, I would read about the major changes between the two versions. There are some significant differences, such as SSIS versus DTS, depending on your environment.
Then, download and run the SQL 2005 advisor. Try to fix all the Errors. You can also pre-install some pre-requists, such as .Net framework on each node.
If all is good, fail over cluster groups onto one node and run the installation from there. pay attention to be logged with an Admin account on both nodes (but log off the second node). Run your installation. If analyzer goes through, you are most likely going to be okay. Choose services you require and remember to read about new DTS support.
Good luck
January 21, 2009 at 11:55 pm
I knew one of my friends did suffer these DRP issues after upgrade, but I couldn't find the ref.
Today I found it back, so here it is:
http://sqlblog.com/blogs/allen_white/archive/2007/10/08/pay-attention-to-cluster-setup.aspx#11345
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 23, 2009 at 8:35 am
Did inplace upgrade
when running the Install it looked like it upgraded node2 also,
while applying sp2 to Node1 I got Failure status for Database Services Component, rest all components
were ended successfully,
when I googled for this I found out that it's a bug in SP2.
BUG: The Installation Progress dialog box displays a status of Failure for the
Database Services component when you install SQL Server 2005 Service Pack 1 or
SQL Server 2005 Service Pack 2 on an instance of SQL Server 2005
Did anybody faced same problem.How did you resolve this?
Thanks in advance
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply