Help to verify ?

I do a SQL migration. Help to verify whether it's OK.
Old Server: SVR1, SQL Server Enterprise edition
New Server: SVR2, SQL Server Enterprise Edition
There are many user databases and linked server in SVR1,
it's inconvenient to copy database file and attach to new
server. And also need to create user account, etc. Because
all user database registeration info are stored in master
database, so I try to modify master database. Following is
the procedure:
1.At SVR1, set using SQL authentication, stop SQL server.
copy all system and user database to SVR2, save at
c:\olddata
2.At SVR2, attach master.mdf and mastlog.ldf in c:\olddata
as masternew.
3.In three table sysdatabases, sysaltfiles, sysdevices of
masternew database, modify old path to the real path
c:\sqldata.
4.At SVR2, stop all SQL service, copy all file from
c:\oldpath to c:\sqldata, select yes if need to confirm
file replace
5.At SVR2, start SQL Service, use SQL Query analyzer, run
following script:
exec sp_dropserver 'SVR1'
go
exec sp_addserver 'SVR2','local'
go
6.Open SQL Server Enterprise Manager, it seems all is ok.
Is there any problem to do like this? Or I need to do any
more? Your message to me is my pleasure.Hi
The following article describes how to transfer over to a new server
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546#2
If you followed the steps then there would be no need copy the master
database, but the following article details how to:
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b224071
Your process does not seem to transfer any jobs
John
"ronggui" <ronggui999@.hotmail.com> wrote in message
news:001601c34967$c1a43850$a601280a@.phx.gbl...
> I do a SQL migration. Help to verify whether it's OK.
> Old Server: SVR1, SQL Server Enterprise edition
> New Server: SVR2, SQL Server Enterprise Edition
> There are many user databases and linked server in SVR1,
> it's inconvenient to copy database file and attach to new
> server. And also need to create user account, etc. Because
> all user database registeration info are stored in master
> database, so I try to modify master database. Following is
> the procedure:
> 1.At SVR1, set using SQL authentication, stop SQL server.
> copy all system and user database to SVR2, save at
> c:\olddata
> 2.At SVR2, attach master.mdf and mastlog.ldf in c:\olddata
> as masternew.
> 3.In three table sysdatabases, sysaltfiles, sysdevices of
> masternew database, modify old path to the real path
> c:\sqldata.
> 4.At SVR2, stop all SQL service, copy all file from
> c:\oldpath to c:\sqldata, select yes if need to confirm
> file replace
> 5.At SVR2, start SQL Service, use SQL Query analyzer, run
> following script:
> exec sp_dropserver 'SVR1'
> go
> exec sp_addserver 'SVR2','local'
> go
> 6.Open SQL Server Enterprise Manager, it seems all is ok.
> Is there any problem to do like this? Or I need to do any
> more? Your message to me is my pleasure.
>|||Hi,
Because in new server SVR2, there is already a master
database. I want to change all the old paths in the master
database from old server SVR1, so I attached as masternew.
By the way, at old server SVR1 system and user databases
are saved in different path, I need changing path in
master, so it can work in new server SVR2.
After changing path, I stop SQL Server SVR2, and copy all
old files to exact location.
>--Original Message--
>You attached the master database as "Masternew". I
>thought the master database must be called "Master".
>I will only copy all the databases to the exact location
>in SVR2 including "Master", "Msdb" etc as SVR1.
>.
>|||Hi
The articles do show how to move the master database, you should follow that
procedure.
John
"ronggui" <ronggui999@.hotmail.com> wrote in message
news:040b01c349b0$cab4bca0$a301280a@.phx.gbl...
> Hi,
> Because in new server SVR2, there is already a master
> database. I want to change all the old paths in the master
> database from old server SVR1, so I attached as masternew.
> By the way, at old server SVR1 system and user databases
> are saved in different path, I need changing path in
> master, so it can work in new server SVR2.
> After changing path, I stop SQL Server SVR2, and copy all
> old files to exact location.
> >--Original Message--
> >You attached the master database as "Masternew". I
> >thought the master database must be called "Master".
> >
> >I will only copy all the databases to the exact location
> >in SVR2 including "Master", "Msdb" etc as SVR1.
> >.
> >