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 SQL server installation from one Drive letter to another.

I'm hoping you can help a newbie with a quick question. I need to move
an installation of SQL server 2000 sp3a on a Win2003 Standard server
from the C Drive to the D drive. I'm running out of room on the C Drive
and have more then enough room on the D drive. I know you can detach
databases and move the files and attach them again but I'm looking to
move the whole "C:\Program Files\Microsoft SQL Server" folder to
"D:\Program Files\Microsoft SQL Server"
Is this possible and if so how do you do it? I've seen web pages on how
to move an installation of SQL server from one server to another but
that is not what I'm needing to do.
Thanks in advance,
NathanMoving the complete folder \Program Files\Microsoft SQL Server will pretty
much require a reinstall, if you want to be safe. Just moving the data and
log files ( see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224071) and the
backups, will leave with a more or less basic install of SQL Server, which
takes about 250 MB. That might solve your needs.
--
Jacco Schalkwijk
SQL Server MVP
<nbheck@.hotmail.com> wrote in message
news:1111037005.791634.315720@.z14g2000cwz.googlegroups.com...
> I'm hoping you can help a newbie with a quick question. I need to move
> an installation of SQL server 2000 sp3a on a Win2003 Standard server
> from the C Drive to the D drive. I'm running out of room on the C Drive
> and have more then enough room on the D drive. I know you can detach
> databases and move the files and attach them again but I'm looking to
> move the whole "C:\Program Files\Microsoft SQL Server" folder to
> "D:\Program Files\Microsoft SQL Server"
> Is this possible and if so how do you do it? I've seen web pages on how
> to move an installation of SQL server from one server to another but
> that is not what I'm needing to do.
> Thanks in advance,
> Nathan
>

Moving SQL server installation from one Drive letter to another.

I'm hoping you can help a newbie with a quick question. I need to move
an installation of SQL server 2000 sp3a on a Win2003 Standard server
from the C Drive to the D drive. I'm running out of room on the C Drive
and have more then enough room on the D drive. I know you can detach
databases and move the files and attach them again but I'm looking to
move the whole "C:\Program Files\Microsoft SQL Server" folder to
"D:\Program Files\Microsoft SQL Server"
Is this possible and if so how do you do it? I've seen web pages on how
to move an installation of SQL server from one server to another but
that is not what I'm needing to do.
Thanks in advance,
Nathan
Moving the complete folder \Program Files\Microsoft SQL Server will pretty
much require a reinstall, if you want to be safe. Just moving the data and
log files ( see
http://support.microsoft.com/default...;en-us;Q224071) and the
backups, will leave with a more or less basic install of SQL Server, which
takes about 250 MB. That might solve your needs.
Jacco Schalkwijk
SQL Server MVP
<nbheck@.hotmail.com> wrote in message
news:1111037005.791634.315720@.z14g2000cwz.googlegr oups.com...
> I'm hoping you can help a newbie with a quick question. I need to move
> an installation of SQL server 2000 sp3a on a Win2003 Standard server
> from the C Drive to the D drive. I'm running out of room on the C Drive
> and have more then enough room on the D drive. I know you can detach
> databases and move the files and attach them again but I'm looking to
> move the whole "C:\Program Files\Microsoft SQL Server" folder to
> "D:\Program Files\Microsoft SQL Server"
> Is this possible and if so how do you do it? I've seen web pages on how
> to move an installation of SQL server from one server to another but
> that is not what I'm needing to do.
> Thanks in advance,
> Nathan
>

Moving SQL server installation from one Drive letter to another.

I'm hoping you can help a newbie with a quick question. I need to move
an installation of SQL server 2000 sp3a on a Win2003 Standard server
from the C Drive to the D drive. I'm running out of room on the C Drive
and have more then enough room on the D drive. I know you can detach
databases and move the files and attach them again but I'm looking to
move the whole "C:\Program Files\Microsoft SQL Server" folder to
"D:\Program Files\Microsoft SQL Server"
Is this possible and if so how do you do it? I've seen web pages on how
to move an installation of SQL server from one server to another but
that is not what I'm needing to do.
Thanks in advance,
NathanMoving the complete folder \Program Files\Microsoft SQL Server will pretty
much require a reinstall, if you want to be safe. Just moving the data and
log files ( see
http://support.microsoft.com/defaul...b;en-us;Q224071) and the
backups, will leave with a more or less basic install of SQL Server, which
takes about 250 MB. That might solve your needs.
Jacco Schalkwijk
SQL Server MVP
<nbheck@.hotmail.com> wrote in message
news:1111037005.791634.315720@.z14g2000cwz.googlegroups.com...
> I'm hoping you can help a newbie with a quick question. I need to move
> an installation of SQL server 2000 sp3a on a Win2003 Standard server
> from the C Drive to the D drive. I'm running out of room on the C Drive
> and have more then enough room on the D drive. I know you can detach
> databases and move the files and attach them again but I'm looking to
> move the whole "C:\Program Files\Microsoft SQL Server" folder to
> "D:\Program Files\Microsoft SQL Server"
> Is this possible and if so how do you do it? I've seen web pages on how
> to move an installation of SQL server from one server to another but
> that is not what I'm needing to do.
> Thanks in advance,
> Nathan
>

Moving replicated database to a new machine

Hello.
I'm running SQL Server 2000 (sp3a) and am moving the installation to a new
machine one database at a time (by using Backup/Restore). The new machine
and SQL installation also has a new name that is being kept.
The databases that I've moved thus far are not replicated databases so it's
been easy.
I'm uncertain about this approach when it comes to replicated databases. I
can find no information on Microsoft's site when it comes to moving a
"replicated" database other than a mention of it in one of their KB
articles, and it says something like "Find and read more information about
moving replicated databases", and that's it.
All input is welcome.
Thanks in advance,
Mike
Mike,
are you moving the publisher or subscriber? Is the new box named the same?
Is it in the same domain/trust relationship? Are the service startup
accounts the same? These are all important variables in deciding which way
to do it, or if it is even possible.
Regards,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
"Mike Lopez" <MichaelLopez@.Emmerel.com> wrote in message
news:eAaZ6gJnEHA.3564@.tk2msftngp13.phx.gbl...
> Hello.
> I'm running SQL Server 2000 (sp3a) and am moving the installation to a new
> machine one database at a time (by using Backup/Restore). The new machine
> and SQL installation also has a new name that is being kept.
> The databases that I've moved thus far are not replicated databases so
it's
> been easy.
> I'm uncertain about this approach when it comes to replicated databases. I
> can find no information on Microsoft's site when it comes to moving a
> "replicated" database other than a mention of it in one of their KB
> articles, and it says something like "Find and read more information about
> moving replicated databases", and that's it.
> All input is welcome.
> Thanks in advance,
> Mike
>
|||Hi Paul. Thanks for the response.
I'm moving the publisher. The new box is named differently. Same
domain/trust. Service startup accounts are the same (domain account)..
Furthermore the distributor is a separate machine. That machine acts as both
the distributor and subscriber machine.
In my humble opinion the difference in the machine names are the deal
breaker.
What's your thoughts?
Thanks again,
Mike
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:e5V%23XrJnEHA.2864@.tk2msftngp13.phx.gbl...
> Mike,
> are you moving the publisher or subscriber? Is the new box named the same?
> Is it in the same domain/trust relationship? Are the service startup
> accounts the same? These are all important variables in deciding which way
> to do it, or if it is even possible.
> Regards,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
> "Mike Lopez" <MichaelLopez@.Emmerel.com> wrote in message
> news:eAaZ6gJnEHA.3564@.tk2msftngp13.phx.gbl...
> it's
>
|||Mike,
from experience I agree. Replication enters the servername in several system
tables, which then breaks it if you move the publisher to another,
differently named server. Most people script out the publication, move the
publishing database to the new server, modify the script with the new
servername and logins and recreate the publication on the new server. You
may be able to do a nosync initialization in this case, provided you
synchronize before moving the database and prevent any modifications.
Regards,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi again, Paul.
Yeah, that's pretty much what I was thinking.
I didn't realize that it was possible to do a nosynch initialization. That's
good because two of these databases are huge, and I spent a weekend setting
them up for replication the first time.
Thanks again,
Mike
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%233Sy9ZKnEHA.2764@.TK2MSFTNGP10.phx.gbl...
> Mike,
> from experience I agree. Replication enters the servername in several
> system
> tables, which then breaks it if you move the publisher to another,
> differently named server. Most people script out the publication, move the
> publishing database to the new server, modify the script with the new
> servername and logins and recreate the publication on the new server. You
> may be able to do a nosync initialization in this case, provided you
> synchronize before moving the database and prevent any modifications.
> Regards,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>