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 |
|
chulheekim
Starting Member
46 Posts |
 Posted - 2011-01-14 : 18:49:36
|
| I have a sql server 2000 where a user database is residing to support web order applications. I have a lot of dts packages and sql jobs running against the database. We're planning to move the sql server to a new machine. There will be no sql server upgrade. Here's what I'm going to do for the migration. See if you have any concern.1. Install sql server 2000 to the new machine and have the same configurations set up as in the old machine.2. stop both the sql servers.3. Backup the user and system databases from the old server.4. restore them to the new server.5. Start the new sql server.Here's one thing that concerns me a little. For some reason, the new sql server will have a different instance name. Will this cause any problem to the DTS packages, scheduled jobs, and logins that will be moved in the new machine? Will the DTS jobs be running fine under the new server? |
|
|
dataguru1971
Master Smack Fu Yak Hacker
1464 Posts |
Posted - 2011-01-14 : 19:31:47
|
The DTS jobs and programs will need to be configured to point to the new name. The server name is a critical component of how all that stuff connects. You can possibly use configurations to create ALIAS references for the new one to the old name.http://www.mssqltips.com/tip.asp?tip=1620. If you do alias the new one to the old name, you will have to concurrently alias the old server to a different name..but there will likely be a lot of testing required..it won't be plug and play, and would actually be far better if you had all of the connecting configurations change so you can verify that all apps and connections have properly migrated. If DTS is connecting to (Local) instead of the named instance, those "might" be okay..Keep this in mind for any other SQL servers which may linked..those links will also be broken.
Poor planning on your part does not constitute an emergency on my part. |
 |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-01-16 : 11:10:09
|
| Also, you have to do the backups BEFORE you stop SQL Server. And if any of the databases are not in simple recovery, don't forget the log backups.You'll need to map the logins and users on the new machine as well. |
|
|
|
|
|
|
Sql server 2000 move from old machine to new