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 |
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
 Posted - 2002-11-27 : 10:35:30
|
| Hey all,We're finally getting to migrate to the 2000's. Currently planning is to go to Win 2K, get stable on that for a few months, then mograte to to SQL 2K. My question is: anyone know of any specific concern's/gotcha's for the Win 2K upgrade ?I'll sketch our environment: Current SQL 7 SP 2 on NT 4 SP5. 4 main DB's, one of which is currently 200 GB (other ar minor). Obviously, this process must have no/low impact on users, and as such is targeted for a long weekend. Target is to go to Win 2K SP2.The server upgrade is being done by the company who have the "infrastructure" contract - we won't have a hand in the actual "doing" but can raise concern's and issues, which is what I'm looking for. The "infrastructure" company plan to simply upgrade NT4 to Win 2K.Obviously we will make a full backup the DB's, and move off the server.TIA for any commentsCiaoChaos, Disorder and Panic ... my work is done here! |
|
|
royv
Constraint Violating Yak Guru
455 Posts |
Posted - 2002-11-27 : 11:04:55
|
| If you are going to make full backups and move to another server, why don't you reformat the box and make a clean install? This would be the best way to insure minimal problems and optimal performance, at least in my opinion. Once the install is complete, you can then reinstall SQL 7 and restore the databases. You obviously would have to consider user logins and similar installation procedures of SQL 7 to make sure that the databases would restore properly. Hope I'm not missing anything, but before you do this, TEST, TEST, TEST, and then TEST SOME MORE!!!!***************************************Death must absolutely come to enemies of the code! |
 |
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2002-11-27 : 11:29:58
|
| Our infrastructure people have decided to go the "upgrade" route, which does give me concerns - hence my question. Their concern is that we have EMC external storage that our DB's reside upon, and that NT writes some kind of signiture file for this. When we DRP (disater recovery process) they have found that it is necessary to go to exact match of C: and D:, else NT will apparently bascially "dump" the E: (this is the External emc array) and "clean" it. I.e. we have no DB's etc. This DRP has been done a few times in the last couple of months - we build a "duplicate" or "clone" of the production server, off of the network, then take prod down, and plug everything into the clone, which then becomes the prod box. I know , I know - use CLUSTERS !!! If only we could, but between the infrastructure company, and the application vendor (the apllication is a 3rd party product, customized partly for our environment), and the business (don't want to pay for "un-used server's), we don't have a cluster environment. Anyway, back to the problem/question. Apparently they seem to think an windows upgrade process doesn't have this problem (I guess it inherits or migrates the signiture file somehow).Thanx for the initial response - anything further ??Ps - testing - definitely - we have aroudn 13 dev/test/QA/etc. etc server that will be test-beds first....Chaos, Disorder and Panic ... my work is done here! |
|
|
|
|
|
|
|
|
SQl 7 on NT - upgrade to Win 2K. Any gotcha's ?