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 |
|
steelkilt
Constraint Violating Yak Guru
255 Posts |
 Posted - 2005-08-01 : 16:07:51
|
| I finally have to face the music. Everyone in my shop is moving to Win 2003.I'm currently running SQL Server 7.0 on Win 2000 server (rather comfortably I might add ;-)I have a staging machine I can use for testing and I have been told by our support group that the OS should be upgraded first, then SQL server.My main questions:-- anyone have experience with this type of upgrade and/or can point me to links that discuss same?-- potential pitfalls to avoid? I'm most concerned about my SQL 7 dbs being converted properly and the next main area of concern is my classic ASP web apps -- will the 2003 versions of MS OS and SQL server support these?thanks for reading. |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2005-08-01 : 16:12:15
|
| The only issue I ran into when upgrading my cluster from 2000 to 2003 were the differences in MSDTC for clustering. It needs it's own drive resource now! I don't think my experience applies to yoru though. If it does, I think I can provide you some link.Michael<Yoda>Use the Search page you must. Find the answer you will. Cursors, path to the Dark Side they are. Avoid them, you must. Use Order By NewID() to get a random record you will.</Yoda> |
 |
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2005-08-02 : 11:11:21
|
| I'm sure you just got mistaken in your typed message and already know this, but there is no SQL 2003. It's SQL 2000 until SQL 2005 (YUKON) is released.DanielSQL Server DBAwww.dallasteam.com |
|
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2005-08-02 : 17:17:37
|
| Upgrading in place tends to be a bit of a dicey operation, as all the barnacles of various patches, programs, etc. tend to complicate matters for the new operating system. If you can, I would suggest formatting your staging box' disks, and starting with a fresh install of Win2003/sql2k+SP3a. You should be able to restore the 7.0 databases onto this machine (a little internal upgrading will happen), set the db compatibility level to 80, and you should be all set.The web server should not notice much of a difference, especially if you are already using SQLOLEDB providers in your connection strings (ODBC is getting phased out, but should work). Can you check some of these? |
|
|
|
|
|
|
|
|
aack! SQL 7.0/MS Win2k- to- SQL 2003/MS Win 2003