SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Is it safe to upgrade OS without testing???
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

DBADave
Constraint Violating Yak Guru

USA
366 Posts

Posted - 10/06/2005 :  16:08:41  Show Profile  Reply with Quote
I have always upgraded the OS on test servers before upgrading on production. We are in the process of upgrading hardware for a production server and are considering installing Windows Server 2003 Standard Edition vs. what previously existed on the server, Windows 2000 Standard Edition. How much of a risk would this present? I'm leaning towards not changing the OS until we have a chance to upgrade the test servers first.

Dave

stprsbk
Starting Member

2 Posts

Posted - 10/06/2005 :  16:16:47  Show Profile  Reply with Quote
If you are going to upgrade straight from 2000 to 2003 server I would make sure I have a good backup of everything on the server. While upgrades tend to work much of the time there is the occational time when it goes wrong.

I prefer to install a fresh OS rather than upgrading OS's on the same box.
Go to Top of Page

eyechart
Flowing Fount of Yak Knowledge

USA
3575 Posts

Posted - 10/06/2005 :  16:24:34  Show Profile  Reply with Quote
I haven't had any problems moving from win2k to win2k3. Actually, in our testing 2k3 seems to be more reliable and is still actively supported by microsoft. Win2k is no longer supported with bugfixes, only security hotfixes are available. We are starting to have some pretty severe issues with our win2k boxes, especially with the latest security hotfixes.

As for your upgrade, I would make sure that you have a good backup as well as copies of the database datafiles (made while the database was shutdown).

Also, I would definitely not perform and upgrade of the OS. I would go with a clean installation. I cannot stress how important it is to make sure you have several sets of backups so you don't have a problem with a corrupt backup.


-ec
Go to Top of Page

bakerjon
Posting Yak Master

USA
145 Posts

Posted - 10/06/2005 :  17:21:21  Show Profile  Visit bakerjon's Homepage  Reply with Quote
I think the only think I've run into is the MSDTC Network access difference in Windows 2003. It's off by default. SP1 also introduced some changes to the security of MSDTC. This would not be a problem if the application does not use distributed transactions, though.

Like a kidney stone, this too shall pass.
Go to Top of Page

derrickleggett
Pointy Haired Yak DBA

USA
4184 Posts

Posted - 10/06/2005 :  20:42:01  Show Profile  Visit derrickleggett's Homepage  Send derrickleggett an AOL message  Send derrickleggett a Yahoo! Message  Reply with Quote
I'm going to say this everywhere you posted. I think 2003 is much more stable. You do have to fix the DTC access issues for a lot of applications to work. I would NEVER upgrade production without upgrading test first and doing a full test. Anyone who does this is careless and deserves all the fallout that happens when they bring production down and cause their company to lose revenue.

Just my .5 cent worth.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page

Kristen
Test

United Kingdom
22415 Posts

Posted - 10/07/2005 :  01:57:51  Show Profile  Reply with Quote
Although this has nothing to do with testing the "update production in situ" didn't work for this guy, even with good backups!

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=56098

So it needs the backups restored onto another server to prove that they are readable.

One would assume that upgrading the O/S in situ will leave the applications alone ... so you should not have to restore. But I always favour formatting the machine at an O/S upgrade - to get rid of all the DLL rot in the registry etc.

Kristen
Go to Top of Page

DBADave
Constraint Violating Yak Guru

USA
366 Posts

Posted - 10/07/2005 :  08:53:22  Show Profile  Reply with Quote
Thanks everyone for your feedback. I should have explained the situation a bit better. We're not actually upgrading the OS in place. We purchased a new server and will be installing the OS on a clean drive. We had planned to test the new hardware, but the testing involved in a hardware change is fairly basic since we are primarily concerned with connectivity, performance and security testing. Application functionality testing wouldn't come into play for a new server, assuming the server name, OS and SQL Server versions (including hot fixes and service packs) remained unchanged.

We found the Q article (Q329332) that addressed a problem (the MSDTC issue) with Linked servers and Windows Server 2003. Once I heard about this issue yesterday we decided testing the application functionality was necessary.

I appreciate the feedback.

Dave
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.12 seconds. Powered By: Snitz Forums 2000