Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-11-07 : 09:26:22
|
| edan writes "Is there an article which describes steps and hints or problems with SQL2000 when the Operating System is being upgraded from WIN2k Server to Win2k Advanced Server...Can some one provide a list of 'what-not to do's?Thanks in advanceegavish@snet.net" |
|
|
smccreadie
Aged Yak Warrior
505 Posts |
Posted - 2002-11-07 : 09:42:44
|
| I'm not familiar with an article. However you should BACKUP everything.Best situation is to start with a clean server, install Win2K, patches, then SQL2K. Then you migrate your databases to the new server.May not be an option for you, but do it if you can. |
 |
|
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
Posted - 2002-11-18 : 11:21:13
|
| We ran into a huge bummer. Our Production server uses Windows 2000 Server SP2, SQL 2k, SP1. Our QA DB server which hosts about 10 instances was recently upgraded to Advanced Server to let it exploti the 8GB of RAM.To do this you have to boot the server with /pae option in boot.ini.When we did this, we could use the server without any problems. The performance is great. But you try to copy large files/ restore databases from a non advanced server (which does not use /pae switch). The restore fails.NT Restore, SQL Restore and sometimes even plain old file copy does not go through.Upon researching I found that if the old backups have to be used, we have to disable the /pae switch in boot.ini reboot. finish your restore and put back the /pae switch to function as before.Microsoft is still trying to work this problem out, I was in fact wondering if any of the illustrious colleagues have a simpler and more permanent work around on this... |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
|
|
|
|
|
SQLServer machine is upgraded to Win2k Advanced Server