Moving User Databases from a SQL 2000 SP3a to SP4

Hi All,
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
--
BenYou can do a simple backup/restore or detach/attach. However, for max
uptime, consider log shipping. You're down only for the time it takes to
kick out the users, and copy and restore the last log.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
Hi All,
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
--
Ben|||Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
--
Ben
"Tom Moreau" wrote:
> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live Server
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the current
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to SP4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>|||Yes. Be sure to transfer the logins first, as well as and SQL Server Agent
jobs. You may also want to look at any DTS packages that have the server
name hard-wired.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
--
Ben
"Tom Moreau" wrote:
> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live
> Server
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the
> current
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to
> SP4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>|||Thanks for the update Tom
Will will be transferrring the logins, but creating new maintenance plan
jobs on the SP4 upgraded server.
Will these Maintenance plans work ok on the Databases transferred from the
SP3a server ?
Ben
"Tom Moreau" wrote:
> Yes. Be sure to transfer the logins first, as well as and SQL Server Agent
> jobs. You may also want to look at any DTS packages that have the server
> name hard-wired.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
> Just to confirm - Does that mean we can upgrade the new Server to SP4, then
> restore the user DBs from the SP3a server on to this new one with out any
> issues? Obviusly Backing up the databases before hand and straight after the
> restore
> --
> Ben
>
> "Tom Moreau" wrote:
> > You can do a simple backup/restore or detach/attach. However, for max
> > uptime, consider log shipping. You're down only for the time it takes to
> > kick out the users, and copy and restore the last log.
> >
> > --
> > Tom
> >
> > ----
> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> > SQL Server MVP
> > Columnist, SQL Server Professional
> > Toronto, ON Canada
> > www.pinpub.com
> > ..
> > "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> > news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> > Hi All,
> >
> > I have a recent requirement to move production databases from a Live
> > Server
> > running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> > move this one into production
> >
> > Currently, the new Server is running SQL 2000 SP3a (the same as the
> > current
> > Live SQL server) as we were going to move User Databases to this version
> > until the requirement for SP4 came along.
> >
> > Please can you advise what is the best procedure to acheive this with
> > minimal downtime and risk.
> >
> > - Can User databases be moved to the New Server which has been upgraded to
> > SP4 or do all user databases need to be moved to the SP4 server, then the
> > server upgraded ?
> >
> > - Clearly it would be more straightforward to upgrade the new Server to
> > SP4
> > before moving User databases to it, but do not have info of the issues
> > concered with this.
> >
> > Thanks in advance for you help and I hope to received a speedy response
> >
> > --
> > Ben
> >
> >
>
>

Moving User Databases from a SQL 2000 SP3a to SP4

Hi All,
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
Ben
You can do a simple backup/restore or detach/attach. However, for max
uptime, consider log shipping. You're down only for the time it takes to
kick out the users, and copy and restore the last log.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
Hi All,
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
Ben
|||Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
Ben
"Tom Moreau" wrote:

> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live Server
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the current
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to SP4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>
|||Yes. Be sure to transfer the logins first, as well as and SQL Server Agent
jobs. You may also want to look at any DTS packages that have the server
name hard-wired.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
Ben
"Tom Moreau" wrote:

> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live
> Server
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the
> current
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to
> SP4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>
|||Thanks for the update Tom
Will will be transferrring the logins, but creating new maintenance plan
jobs on the SP4 upgraded server.
Will these Maintenance plans work ok on the Databases transferred from the
SP3a server ?
Ben
"Tom Moreau" wrote:

> Yes. Be sure to transfer the logins first, as well as and SQL Server Agent
> jobs. You may also want to look at any DTS packages that have the server
> name hard-wired.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
> Just to confirm - Does that mean we can upgrade the new Server to SP4, then
> restore the user DBs from the SP3a server on to this new one with out any
> issues? Obviusly Backing up the databases before hand and straight after the
> restore
> --
> Ben
>
> "Tom Moreau" wrote:
>
>

Moving User Databases from a SQL 2000 SP3a to SP4

Hi All,
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
BenYou can do a simple backup/restore or detach/attach. However, for max
uptime, consider log shipping. You're down only for the time it takes to
kick out the users, and copy and restore the last log.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
Hi All,
I have a recent requirement to move production databases from a Live Server
running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
move this one into production
Currently, the new Server is running SQL 2000 SP3a (the same as the current
Live SQL server) as we were going to move User Databases to this version
until the requirement for SP4 came along.
Please can you advise what is the best procedure to acheive this with
minimal downtime and risk.
- Can User databases be moved to the New Server which has been upgraded to
SP4 or do all user databases need to be moved to the SP4 server, then the
server upgraded ?
- Clearly it would be more straightforward to upgrade the new Server to SP4
before moving User databases to it, but do not have info of the issues
concered with this.
Thanks in advance for you help and I hope to received a speedy response
Ben|||Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
Ben
"Tom Moreau" wrote:

> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live Serve
r
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the curren
t
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to SP
4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>|||Yes. Be sure to transfer the logins first, as well as and SQL Server Agent
jobs. You may also want to look at any DTS packages that have the server
name hard-wired.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"Ben P" <BenP@.discussions.microsoft.com> wrote in message
news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
Just to confirm - Does that mean we can upgrade the new Server to SP4, then
restore the user DBs from the SP3a server on to this new one with out any
issues? Obviusly Backing up the databases before hand and straight after the
restore
Ben
"Tom Moreau" wrote:

> You can do a simple backup/restore or detach/attach. However, for max
> uptime, consider log shipping. You're down only for the time it takes to
> kick out the users, and copy and restore the last log.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:B79F8D95-B0A9-46C6-B8C0-5F89BDEF02B9@.microsoft.com...
> Hi All,
> I have a recent requirement to move production databases from a Live
> Server
> running SQL 2000 SP3a to a separate (new) server running SQL 2000 SP4 and
> move this one into production
> Currently, the new Server is running SQL 2000 SP3a (the same as the
> current
> Live SQL server) as we were going to move User Databases to this version
> until the requirement for SP4 came along.
> Please can you advise what is the best procedure to acheive this with
> minimal downtime and risk.
> - Can User databases be moved to the New Server which has been upgraded to
> SP4 or do all user databases need to be moved to the SP4 server, then the
> server upgraded ?
> - Clearly it would be more straightforward to upgrade the new Server to
> SP4
> before moving User databases to it, but do not have info of the issues
> concered with this.
> Thanks in advance for you help and I hope to received a speedy response
> --
> Ben
>|||Thanks for the update Tom
Will will be transferrring the logins, but creating new maintenance plan
jobs on the SP4 upgraded server.
Will these Maintenance plans work ok on the Databases transferred from the
SP3a server ?
Ben
"Tom Moreau" wrote:

> Yes. Be sure to transfer the logins first, as well as and SQL Server Agen
t
> jobs. You may also want to look at any DTS packages that have the server
> name hard-wired.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> "Ben P" <BenP@.discussions.microsoft.com> wrote in message
> news:C1760DC8-F77A-40D1-BC0E-F4C0146E6118@.microsoft.com...
> Just to confirm - Does that mean we can upgrade the new Server to SP4, the
n
> restore the user DBs from the SP3a server on to this new one with out any
> issues? Obviusly Backing up the databases before hand and straight after t
he
> restore
> --
> Ben
>
> "Tom Moreau" wrote:
>
>
>

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
>
>
>
>