June 12, 2004 at 9:15 pm
Hi ,
Can anyone tell what problems might occurs when I need to move all production databases of windows 2000 sql 2k to a new server with windows 2003 with SQL 2000 sp3 .
Thanks
chami
June 13, 2004 at 9:00 pm
The only problems we've experienced so far are instances where the server was attached to a SAN. Make sure all your hardware is on the W2K3 compatability list and you have ALL the latest drivers.
Derrick Leggett
Mean Old DBA
When life gives you a lemon, fire the DBA.
June 14, 2004 at 3:29 am
Hi,
The following are known issues of SQL Server 2000 on Windows 2003 server.
To run SQL Server on Windows Server 2003, you must have SQL Server 2000 Service Pack 3 (SP3) installed. Windows Server 2003 blocks TCP/IP functionality for named instances that are not running SQL Server 2000 SP3 or later.
- SQL Server 2000 Service Pack 2 (SP2) and earlier are not supported by the Microsoft Windows Server 2003 family
- S Sivaprasad
June 14, 2004 at 8:46 am
Hi Chami,
From a more generic server to server move standpoint, here are a couple of things to consider.
1. If the drive configurations on the two servers are not the same, you'll need to use the WITH MOVE option when restoring the databases.
2. If you have a bunch of SQL Jobs and plan to migrate the MSDB database, you will need to edit the sysjobs table to fix the server name.
3. If you have Standard SQL Logins, you will want to sync them up between the servers. I'm sure there are a couple of scripts in the Script Library for this.
4. If you are not planning on using the same server name, you will need to change connection strings for the applications which use the SQL Server.
I'm sure there are other things, but those are the one's that are off the top of my head.
Regards,
Steve
Meddle not in the affairs of dragons, for you are crunchy and taste good with ketchup.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply