Moving to a new server

We're moving the QA enviornment to a new server and I want to restore the
database backups (including all jobs).
I know I have to restore the application DB's + model. I think I should be
restoring msdb, but I'm unsure about master.
What other "gotchas" are waiting?
Thanks,
JayYou may or may not need to restore the system dbs depending on what you want
to accomplish. If there is nothing in MSDB that you want to keep other than
the jobs I would just script them and run the scripts on the new server.
Have a look at these:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408.aspx Moving system dbs
2005
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's 2000
http://support.microsoft.com/?id=314546 Moving DB's between Servers
http://support.microsoft.com/?id=224071 Moving SQL Server Databases to a
New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/columnists/cBunch/movingyouruserswiththeirdatabases.asp
Moving Users
http://support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to users
http://support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://support.microsoft.com/?id=240872 How to Resolve Permission Issues
When a Database Is Moved Between SQL Servers
http://support.microsoft.com/?id=307775 Disaster Recovery Articles for
SQL Server
http://support.microsoft.com/?id=320125 Moving a Diagram
http://support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Jay" <nospan@.nospam.org> wrote in message
news:uDQ03YzGIHA.4592@.TK2MSFTNGP02.phx.gbl...
> We're moving the QA enviornment to a new server and I want to restore the
> database backups (including all jobs).
> I know I have to restore the application DB's + model. I think I should be
> restoring msdb, but I'm unsure about master.
> What other "gotchas" are waiting?
> Thanks,
> Jay
>

moving system db's to new location with different logical drive letters

Hi, my requirement is to move a host of databases (including the systems
databases) to a new storage unit which will have new logical drives. Now I
followed the process of detach/attach as per article:
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/default.aspx?scid=kb;en-us;224071
I managed to move the databases in the order: model, msdb, temp (via ALTER
DATABASE). At this point SQL managed to start.
I then went to perform the master database relocation step via changing the
parameters in the startup parameters in EM, but my SQL would not start. So I
knew it was my master database which was the problem.
What I found was that I could not use the previous master db as it still had
references to model, msdb etc with the old drive letter. I could not simply
move the model and msdb files to this old drive letter as the drive letter
did not exist on the new storage unit.
My questions...
How do I modify my old master to reference the system databases based on the
new drive letters/location?
If i cannot do this, I am guessing I can use the new master db, however I
would need to change some of the system database files referencing in
sysdatabases, sysaltfiles and sysdevices? In addition I would need to script
out my logins as this obviously isnt attached with the new master, but with
the old master. After this process I should be set right?
Any help most appreciated.
Thanks.
JaneWhat I forgot to mention was the fact that these moved databases will not be
referenced by the old SQL server (serverA), but by a new instance of SQL on
another PC (serverB). So what I'm doing is the following:
Old configuration: serverA --> G:\myDatabaseFiles
New configuration: serverB --> Z:\myDatabaseFiles
ServerA cannot see Z: drive
ServerB cannot see G: drive
Any help most appreciated.
Kindest regards,
Jane
"Jane Richardson" <J.Richardson@.melgrave.com.au> wrote in message
news:e2Q$dge8FHA.500@.TK2MSFTNGP15.phx.gbl...
> Hi, my requirement is to move a host of databases (including the systems
> databases) to a new storage unit which will have new logical drives. Now I
> followed the process of detach/attach as per article:
> Moving SQL Server databases to a new location with Detach/Attach
> http://support.microsoft.com/default.aspx?scid=kb;en-us;224071
> I managed to move the databases in the order: model, msdb, temp (via ALTER
> DATABASE). At this point SQL managed to start.
> I then went to perform the master database relocation step via changing
> the parameters in the startup parameters in EM, but my SQL would not
> start. So I knew it was my master database which was the problem.
> What I found was that I could not use the previous master db as it still
> had references to model, msdb etc with the old drive letter. I could not
> simply move the model and msdb files to this old drive letter as the drive
> letter did not exist on the new storage unit.
> My questions...
> How do I modify my old master to reference the system databases based on
> the new drive letters/location?
> If i cannot do this, I am guessing I can use the new master db, however I
> would need to change some of the system database files referencing in
> sysdatabases, sysaltfiles and sysdevices? In addition I would need to
> script out my logins as this obviously isnt attached with the new master,
> but with the old master. After this process I should be set right?
> Any help most appreciated.
> Thanks.
> Jane
>
>
>
>

moving system db's to new location with different logical drive letters

Hi, my requirement is to move a host of databases (including the systems
databases) to a new storage unit which will have new logical drives. Now I
followed the process of detach/attach as per article:
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/default...b;en-us;224071
I managed to move the databases in the order: model, msdb, temp (via ALTER
DATABASE). At this point SQL managed to start.
I then went to perform the master database relocation step via changing the
parameters in the startup parameters in EM, but my SQL would not start. So I
knew it was my master database which was the problem.
What I found was that I could not use the previous master db as it still had
references to model, msdb etc with the old drive letter. I could not simply
move the model and msdb files to this old drive letter as the drive letter
did not exist on the new storage unit.
My questions...
How do I modify my old master to reference the system databases based on the
new drive letters/location?
If i cannot do this, I am guessing I can use the new master db, however I
would need to change some of the system database files referencing in
sysdatabases, sysaltfiles and sysdevices? In addition I would need to script
out my logins as this obviously isnt attached with the new master, but with
the old master. After this process I should be set right?
Any help most appreciated.
Thanks.
Jane
What I forgot to mention was the fact that these moved databases will not be
referenced by the old SQL server (serverA), but by a new instance of SQL on
another PC (serverB). So what I'm doing is the following:
Old configuration: serverA --> G:\myDatabaseFiles
New configuration: serverB --> Z:\myDatabaseFiles
ServerA cannot see Z: drive
ServerB cannot see G: drive
Any help most appreciated.
Kindest regards,
Jane
"Jane Richardson" <J.Richardson@.melgrave.com.au> wrote in message
news:e2Q$dge8FHA.500@.TK2MSFTNGP15.phx.gbl...
> Hi, my requirement is to move a host of databases (including the systems
> databases) to a new storage unit which will have new logical drives. Now I
> followed the process of detach/attach as per article:
> Moving SQL Server databases to a new location with Detach/Attach
> http://support.microsoft.com/default...b;en-us;224071
> I managed to move the databases in the order: model, msdb, temp (via ALTER
> DATABASE). At this point SQL managed to start.
> I then went to perform the master database relocation step via changing
> the parameters in the startup parameters in EM, but my SQL would not
> start. So I knew it was my master database which was the problem.
> What I found was that I could not use the previous master db as it still
> had references to model, msdb etc with the old drive letter. I could not
> simply move the model and msdb files to this old drive letter as the drive
> letter did not exist on the new storage unit.
> My questions...
> How do I modify my old master to reference the system databases based on
> the new drive letters/location?
> If i cannot do this, I am guessing I can use the new master db, however I
> would need to change some of the system database files referencing in
> sysdatabases, sysaltfiles and sysdevices? In addition I would need to
> script out my logins as this obviously isnt attached with the new master,
> but with the old master. After this process I should be set right?
> Any help most appreciated.
> Thanks.
> Jane
>
>
>
>
sql

moving system db's to new location with different logical drive letters

Hi, my requirement is to move a host of databases (including the systems
databases) to a new storage unit which will have new logical drives. Now I
followed the process of detach/attach as per article:
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/defaul...kb;en-us;224071
I managed to move the databases in the order: model, msdb, temp (via ALTER
DATABASE). At this point SQL managed to start.
I then went to perform the master database relocation step via changing the
parameters in the startup parameters in EM, but my SQL would not start. So I
knew it was my master database which was the problem.
What I found was that I could not use the previous master db as it still had
references to model, msdb etc with the old drive letter. I could not simply
move the model and msdb files to this old drive letter as the drive letter
did not exist on the new storage unit.
My questions...
How do I modify my old master to reference the system databases based on the
new drive letters/location?
If i cannot do this, I am guessing I can use the new master db, however I
would need to change some of the system database files referencing in
sysdatabases, sysaltfiles and sysdevices? In addition I would need to script
out my logins as this obviously isnt attached with the new master, but with
the old master. After this process I should be set right?
Any help most appreciated.
Thanks.
JaneWhat I forgot to mention was the fact that these moved databases will not be
referenced by the old SQL server (serverA), but by a new instance of SQL on
another PC (serverB). So what I'm doing is the following:
Old configuration: serverA --> G:\myDatabaseFiles
New configuration: serverB --> Z:\myDatabaseFiles
ServerA cannot see Z: drive
ServerB cannot see G: drive
Any help most appreciated.
Kindest regards,
Jane
"Jane Richardson" <J.Richardson@.melgrave.com.au> wrote in message
news:e2Q$dge8FHA.500@.TK2MSFTNGP15.phx.gbl...
> Hi, my requirement is to move a host of databases (including the systems
> databases) to a new storage unit which will have new logical drives. Now I
> followed the process of detach/attach as per article:
> Moving SQL Server databases to a new location with Detach/Attach
> http://support.microsoft.com/defaul...kb;en-us;224071
> I managed to move the databases in the order: model, msdb, temp (via ALTER
> DATABASE). At this point SQL managed to start.
> I then went to perform the master database relocation step via changing
> the parameters in the startup parameters in EM, but my SQL would not
> start. So I knew it was my master database which was the problem.
> What I found was that I could not use the previous master db as it still
> had references to model, msdb etc with the old drive letter. I could not
> simply move the model and msdb files to this old drive letter as the drive
> letter did not exist on the new storage unit.
> My questions...
> How do I modify my old master to reference the system databases based on
> the new drive letters/location?
> If i cannot do this, I am guessing I can use the new master db, however I
> would need to change some of the system database files referencing in
> sysdatabases, sysaltfiles and sysdevices? In addition I would need to
> script out my logins as this obviously isnt attached with the new master,
> but with the old master. After this process I should be set right?
> Any help most appreciated.
> Thanks.
> Jane
>
>
>
>

Moving MastLog, msdblog and modelLog

I need to move the transaction logs for all the sql db's (including master,
model and user db's etc) to a seperate drive. Does anyone have any experience
doing this in a sql cluster?
Detach and attach method don't work on this DB
You can use KB : http://support.microsoft.com/?id=224071.
HTH
Franco Conenna [MSFT]
"This posting is provided "AS IS" with no warranties, and confers no rights"
"Scan le Gentil" ha scritto:

> I need to move the transaction logs for all the sql db's (including master,
> model and user db's etc) to a seperate drive. Does anyone have any experience
> doing this in a sql cluster?
> Detach and attach method don't work on this DB
>
|||Thanks.
"Franco Conenna [MSFT]" wrote:
[vbcol=seagreen]
> You can use KB : http://support.microsoft.com/?id=224071.
> HTH
> Franco Conenna [MSFT]
> "This posting is provided "AS IS" with no warranties, and confers no rights"
> "Scan le Gentil" ha scritto: