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
>
Showing posts with label installation. Show all posts
Showing posts with label installation. Show all posts
Wednesday, March 21, 2012
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
>
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
>
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 SQL Server installation (dbs, logins, replication, jobs, DTS etc) to new server
I need to move an entire SQL Server installation (databases, logins,
replication, jobs, DTS etc) to a new physical server.
What method requires the least manual intervention? Ideally I would like to
not have to reenter user passwords, and the replication to pick up with the
remote SQL Servers where it left off etc.
If I restored master, distribution, msdb and all user databases to the new
server, would that recreate the entire state of the SQL Server installation?
Would I also need to rename the new server with the old server's name?
Hi Laurence,
It might be helpful to check out :
http://vyaskn.tripod.com/moving_sql_server.htm
Nathan H. Omukwenyi, MVP [SQL Server]
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:OdQe7zm5GHA.3452@.TK2MSFTNGP05.phx.gbl...
>I need to move an entire SQL Server installation (databases, logins,
>replication, jobs, DTS etc) to a new physical server.
> What method requires the least manual intervention? Ideally I would like
> to not have to reenter user passwords, and the replication to pick up with
> the remote SQL Servers where it left off etc.
> If I restored master, distribution, msdb and all user databases to the new
> server, would that recreate the entire state of the SQL Server
> installation? Would I also need to rename the new server with the old
> server's name?
>
|||I'd also recommend Vyas's reference for the general properties.
Replicationwise, you must have the same servername, or else you'll need to
script out the replication setup, change the references to the server name,
apply the scripts and then initialize the subscribers. If you can name the
new box with the netbios name of the old one before installing SQL Server
and restoring the databases, you should be fine. For this to work, you'll
need to stop replication and take the old server off the domain (or rename
it).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Thanks for both of your replies. I read the article and understand the
technique.
The only thing I am concerned about is where Vyas says "Install the exact
same version of Windows operating system on the new server.". My old server
is Windows 2000 and the new one is Windows 2003. Is it really critical that
the Windows versions are identical? What effect could the Windows version
have within SQL Server?
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23psVtas5GHA.3592@.TK2MSFTNGP05.phx.gbl...
> I'd also recommend Vyas's reference for the general properties.
> Replicationwise, you must have the same servername, or else you'll need to
> script out the replication setup, change the references to the server
> name, apply the scripts and then initialize the subscribers. If you can
> name the new box with the netbios name of the old one before installing
> SQL Server and restoring the databases, you should be fine. For this to
> work, you'll need to stop replication and take the old server off the
> domain (or rename it).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
|||My guess is that he is referring to memory/processor settings which are
restricted by the windows installation. These are partially configured in
the master database using sp_configure, and if you are restoring the master
database there'll be some dependency there. Alternatively, he might have
been referring to MS DTC (used in immediate updating subscribers for
replication) or windows firewall settings if these defaults are different on
different windows versions.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
replication, jobs, DTS etc) to a new physical server.
What method requires the least manual intervention? Ideally I would like to
not have to reenter user passwords, and the replication to pick up with the
remote SQL Servers where it left off etc.
If I restored master, distribution, msdb and all user databases to the new
server, would that recreate the entire state of the SQL Server installation?
Would I also need to rename the new server with the old server's name?
Hi Laurence,
It might be helpful to check out :
http://vyaskn.tripod.com/moving_sql_server.htm
Nathan H. Omukwenyi, MVP [SQL Server]
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:OdQe7zm5GHA.3452@.TK2MSFTNGP05.phx.gbl...
>I need to move an entire SQL Server installation (databases, logins,
>replication, jobs, DTS etc) to a new physical server.
> What method requires the least manual intervention? Ideally I would like
> to not have to reenter user passwords, and the replication to pick up with
> the remote SQL Servers where it left off etc.
> If I restored master, distribution, msdb and all user databases to the new
> server, would that recreate the entire state of the SQL Server
> installation? Would I also need to rename the new server with the old
> server's name?
>
|||I'd also recommend Vyas's reference for the general properties.
Replicationwise, you must have the same servername, or else you'll need to
script out the replication setup, change the references to the server name,
apply the scripts and then initialize the subscribers. If you can name the
new box with the netbios name of the old one before installing SQL Server
and restoring the databases, you should be fine. For this to work, you'll
need to stop replication and take the old server off the domain (or rename
it).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Thanks for both of your replies. I read the article and understand the
technique.
The only thing I am concerned about is where Vyas says "Install the exact
same version of Windows operating system on the new server.". My old server
is Windows 2000 and the new one is Windows 2003. Is it really critical that
the Windows versions are identical? What effect could the Windows version
have within SQL Server?
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23psVtas5GHA.3592@.TK2MSFTNGP05.phx.gbl...
> I'd also recommend Vyas's reference for the general properties.
> Replicationwise, you must have the same servername, or else you'll need to
> script out the replication setup, change the references to the server
> name, apply the scripts and then initialize the subscribers. If you can
> name the new box with the netbios name of the old one before installing
> SQL Server and restoring the databases, you should be fine. For this to
> work, you'll need to stop replication and take the old server off the
> domain (or rename it).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
|||My guess is that he is referring to memory/processor settings which are
restricted by the windows installation. These are partially configured in
the master database using sp_configure, and if you are restoring the master
database there'll be some dependency there. Alternatively, he might have
been referring to MS DTC (used in immediate updating subscribers for
replication) or windows firewall settings if these defaults are different on
different windows versions.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Moving SQL Server installation (dbs, logins, replication, jobs, DTS etc) to new server
I need to move an entire SQL Server installation (databases, logins,
replication, jobs, DTS etc) to a new physical server.
What method requires the least manual intervention? Ideally I would like to
not have to reenter user passwords, and the replication to pick up with the
remote SQL Servers where it left off etc.
If I restored master, distribution, msdb and all user databases to the new
server, would that recreate the entire state of the SQL Server installation?
Would I also need to rename the new server with the old server's name?
Hi Laurence,
It might be helpful to check out :
http://vyaskn.tripod.com/moving_sql_server.htm
Nathan H. Omukwenyi, MVP [SQL Server]
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:OdQe7zm5GHA.3452@.TK2MSFTNGP05.phx.gbl...
>I need to move an entire SQL Server installation (databases, logins,
>replication, jobs, DTS etc) to a new physical server.
> What method requires the least manual intervention? Ideally I would like
> to not have to reenter user passwords, and the replication to pick up with
> the remote SQL Servers where it left off etc.
> If I restored master, distribution, msdb and all user databases to the new
> server, would that recreate the entire state of the SQL Server
> installation? Would I also need to rename the new server with the old
> server's name?
>
|||I'd also recommend Vyas's reference for the general properties.
Replicationwise, you must have the same servername, or else you'll need to
script out the replication setup, change the references to the server name,
apply the scripts and then initialize the subscribers. If you can name the
new box with the netbios name of the old one before installing SQL Server
and restoring the databases, you should be fine. For this to work, you'll
need to stop replication and take the old server off the domain (or rename
it).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Thanks for both of your replies. I read the article and understand the
technique.
The only thing I am concerned about is where Vyas says "Install the exact
same version of Windows operating system on the new server.". My old server
is Windows 2000 and the new one is Windows 2003. Is it really critical that
the Windows versions are identical? What effect could the Windows version
have within SQL Server?
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23psVtas5GHA.3592@.TK2MSFTNGP05.phx.gbl...
> I'd also recommend Vyas's reference for the general properties.
> Replicationwise, you must have the same servername, or else you'll need to
> script out the replication setup, change the references to the server
> name, apply the scripts and then initialize the subscribers. If you can
> name the new box with the netbios name of the old one before installing
> SQL Server and restoring the databases, you should be fine. For this to
> work, you'll need to stop replication and take the old server off the
> domain (or rename it).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
|||My guess is that he is referring to memory/processor settings which are
restricted by the windows installation. These are partially configured in
the master database using sp_configure, and if you are restoring the master
database there'll be some dependency there. Alternatively, he might have
been referring to MS DTC (used in immediate updating subscribers for
replication) or windows firewall settings if these defaults are different on
different windows versions.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
sql
replication, jobs, DTS etc) to a new physical server.
What method requires the least manual intervention? Ideally I would like to
not have to reenter user passwords, and the replication to pick up with the
remote SQL Servers where it left off etc.
If I restored master, distribution, msdb and all user databases to the new
server, would that recreate the entire state of the SQL Server installation?
Would I also need to rename the new server with the old server's name?
Hi Laurence,
It might be helpful to check out :
http://vyaskn.tripod.com/moving_sql_server.htm
Nathan H. Omukwenyi, MVP [SQL Server]
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:OdQe7zm5GHA.3452@.TK2MSFTNGP05.phx.gbl...
>I need to move an entire SQL Server installation (databases, logins,
>replication, jobs, DTS etc) to a new physical server.
> What method requires the least manual intervention? Ideally I would like
> to not have to reenter user passwords, and the replication to pick up with
> the remote SQL Servers where it left off etc.
> If I restored master, distribution, msdb and all user databases to the new
> server, would that recreate the entire state of the SQL Server
> installation? Would I also need to rename the new server with the old
> server's name?
>
|||I'd also recommend Vyas's reference for the general properties.
Replicationwise, you must have the same servername, or else you'll need to
script out the replication setup, change the references to the server name,
apply the scripts and then initialize the subscribers. If you can name the
new box with the netbios name of the old one before installing SQL Server
and restoring the databases, you should be fine. For this to work, you'll
need to stop replication and take the old server off the domain (or rename
it).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Thanks for both of your replies. I read the article and understand the
technique.
The only thing I am concerned about is where Vyas says "Install the exact
same version of Windows operating system on the new server.". My old server
is Windows 2000 and the new one is Windows 2003. Is it really critical that
the Windows versions are identical? What effect could the Windows version
have within SQL Server?
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23psVtas5GHA.3592@.TK2MSFTNGP05.phx.gbl...
> I'd also recommend Vyas's reference for the general properties.
> Replicationwise, you must have the same servername, or else you'll need to
> script out the replication setup, change the references to the server
> name, apply the scripts and then initialize the subscribers. If you can
> name the new box with the netbios name of the old one before installing
> SQL Server and restoring the databases, you should be fine. For this to
> work, you'll need to stop replication and take the old server off the
> domain (or rename it).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
|||My guess is that he is referring to memory/processor settings which are
restricted by the windows installation. These are partially configured in
the master database using sp_configure, and if you are restoring the master
database there'll be some dependency there. Alternatively, he might have
been referring to MS DTC (used in immediate updating subscribers for
replication) or windows firewall settings if these defaults are different on
different windows versions.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
sql
Moving SQL Server installation (dbs, logins, replication, jobs, DTS etc) to new server
I need to move an entire SQL Server installation (databases, logins,
replication, jobs, DTS etc) to a new physical server.
What method requires the least manual intervention? Ideally I would like to
not have to reenter user passwords, and the replication to pick up with the
remote SQL Servers where it left off etc.
If I restored master, distribution, msdb and all user databases to the new
server, would that recreate the entire state of the SQL Server installation?
Would I also need to rename the new server with the old server's name?Hi Laurence,
It might be helpful to check out :
http://vyaskn.tripod.com/moving_sql_server.htm
Nathan H. Omukwenyi, MVP [SQL Server]
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:OdQe7zm5GHA.3452@.TK2MSFTNGP05.phx.gbl...
>I need to move an entire SQL Server installation (databases, logins,
>replication, jobs, DTS etc) to a new physical server.
> What method requires the least manual intervention? Ideally I would like
> to not have to reenter user passwords, and the replication to pick up with
> the remote SQL Servers where it left off etc.
> If I restored master, distribution, msdb and all user databases to the new
> server, would that recreate the entire state of the SQL Server
> installation? Would I also need to rename the new server with the old
> server's name?
>|||I'd also recommend Vyas's reference for the general properties.
Replicationwise, you must have the same servername, or else you'll need to
script out the replication setup, change the references to the server name,
apply the scripts and then initialize the subscribers. If you can name the
new box with the netbios name of the old one before installing SQL Server
and restoring the databases, you should be fine. For this to work, you'll
need to stop replication and take the old server off the domain (or rename
it).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Thanks for both of your replies. I read the article and understand the
technique.
The only thing I am concerned about is where Vyas says "Install the exact
same version of Windows operating system on the new server.". My old server
is Windows 2000 and the new one is Windows 2003. Is it really critical that
the Windows versions are identical? What effect could the Windows version
have within SQL Server?
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23psVtas5GHA.3592@.TK2MSFTNGP05.phx.gbl...
> I'd also recommend Vyas's reference for the general properties.
> Replicationwise, you must have the same servername, or else you'll need to
> script out the replication setup, change the references to the server
> name, apply the scripts and then initialize the subscribers. If you can
> name the new box with the netbios name of the old one before installing
> SQL Server and restoring the databases, you should be fine. For this to
> work, you'll need to stop replication and take the old server off the
> domain (or rename it).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>|||My guess is that he is referring to memory/processor settings which are
restricted by the windows installation. These are partially configured in
the master database using sp_configure, and if you are restoring the master
database there'll be some dependency there. Alternatively, he might have
been referring to MS DTC (used in immediate updating subscribers for
replication) or windows firewall settings if these defaults are different on
different windows versions.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
replication, jobs, DTS etc) to a new physical server.
What method requires the least manual intervention? Ideally I would like to
not have to reenter user passwords, and the replication to pick up with the
remote SQL Servers where it left off etc.
If I restored master, distribution, msdb and all user databases to the new
server, would that recreate the entire state of the SQL Server installation?
Would I also need to rename the new server with the old server's name?Hi Laurence,
It might be helpful to check out :
http://vyaskn.tripod.com/moving_sql_server.htm
Nathan H. Omukwenyi, MVP [SQL Server]
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:OdQe7zm5GHA.3452@.TK2MSFTNGP05.phx.gbl...
>I need to move an entire SQL Server installation (databases, logins,
>replication, jobs, DTS etc) to a new physical server.
> What method requires the least manual intervention? Ideally I would like
> to not have to reenter user passwords, and the replication to pick up with
> the remote SQL Servers where it left off etc.
> If I restored master, distribution, msdb and all user databases to the new
> server, would that recreate the entire state of the SQL Server
> installation? Would I also need to rename the new server with the old
> server's name?
>|||I'd also recommend Vyas's reference for the general properties.
Replicationwise, you must have the same servername, or else you'll need to
script out the replication setup, change the references to the server name,
apply the scripts and then initialize the subscribers. If you can name the
new box with the netbios name of the old one before installing SQL Server
and restoring the databases, you should be fine. For this to work, you'll
need to stop replication and take the old server off the domain (or rename
it).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Thanks for both of your replies. I read the article and understand the
technique.
The only thing I am concerned about is where Vyas says "Install the exact
same version of Windows operating system on the new server.". My old server
is Windows 2000 and the new one is Windows 2003. Is it really critical that
the Windows versions are identical? What effect could the Windows version
have within SQL Server?
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23psVtas5GHA.3592@.TK2MSFTNGP05.phx.gbl...
> I'd also recommend Vyas's reference for the general properties.
> Replicationwise, you must have the same servername, or else you'll need to
> script out the replication setup, change the references to the server
> name, apply the scripts and then initialize the subscribers. If you can
> name the new box with the netbios name of the old one before installing
> SQL Server and restoring the databases, you should be fine. For this to
> work, you'll need to stop replication and take the old server off the
> domain (or rename it).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>|||My guess is that he is referring to memory/processor settings which are
restricted by the windows installation. These are partially configured in
the master database using sp_configure, and if you are restoring the master
database there'll be some dependency there. Alternatively, he might have
been referring to MS DTC (used in immediate updating subscribers for
replication) or windows firewall settings if these defaults are different on
different windows versions.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Moving SQL Server installation (dbs, logins, replication, jobs, DTS etc) to new server
I need to move an entire SQL Server installation (databases, logins,
replication, jobs, DTS etc) to a new physical server.
What method requires the least manual intervention? Ideally I would like to
not have to reenter user passwords, and the replication to pick up with the
remote SQL Servers where it left off etc.
If I restored master, distribution, msdb and all user databases to the new
server, would that recreate the entire state of the SQL Server installation?
Would I also need to rename the new server with the old server's name?Hi Laurence,
It might be helpful to check out :
http://vyaskn.tripod.com/moving_sql_server.htm
Nathan H. Omukwenyi, MVP [SQL Server]
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:OdQe7zm5GHA.3452@.TK2MSFTNGP05.phx.gbl...
>I need to move an entire SQL Server installation (databases, logins,
>replication, jobs, DTS etc) to a new physical server.
> What method requires the least manual intervention? Ideally I would like
> to not have to reenter user passwords, and the replication to pick up with
> the remote SQL Servers where it left off etc.
> If I restored master, distribution, msdb and all user databases to the new
> server, would that recreate the entire state of the SQL Server
> installation? Would I also need to rename the new server with the old
> server's name?
>|||I'd also recommend Vyas's reference for the general properties.
Replicationwise, you must have the same servername, or else you'll need to
script out the replication setup, change the references to the server name,
apply the scripts and then initialize the subscribers. If you can name the
new box with the netbios name of the old one before installing SQL Server
and restoring the databases, you should be fine. For this to work, you'll
need to stop replication and take the old server off the domain (or rename
it).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Thanks for both of your replies. I read the article and understand the
technique.
The only thing I am concerned about is where Vyas says "Install the exact
same version of Windows operating system on the new server.". My old server
is Windows 2000 and the new one is Windows 2003. Is it really critical that
the Windows versions are identical? What effect could the Windows version
have within SQL Server?
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23psVtas5GHA.3592@.TK2MSFTNGP05.phx.gbl...
> I'd also recommend Vyas's reference for the general properties.
> Replicationwise, you must have the same servername, or else you'll need to
> script out the replication setup, change the references to the server
> name, apply the scripts and then initialize the subscribers. If you can
> name the new box with the netbios name of the old one before installing
> SQL Server and restoring the databases, you should be fine. For this to
> work, you'll need to stop replication and take the old server off the
> domain (or rename it).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>|||My guess is that he is referring to memory/processor settings which are
restricted by the windows installation. These are partially configured in
the master database using sp_configure, and if you are restoring the master
database there'll be some dependency there. Alternatively, he might have
been referring to MS DTC (used in immediate updating subscribers for
replication) or windows firewall settings if these defaults are different on
different windows versions.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
replication, jobs, DTS etc) to a new physical server.
What method requires the least manual intervention? Ideally I would like to
not have to reenter user passwords, and the replication to pick up with the
remote SQL Servers where it left off etc.
If I restored master, distribution, msdb and all user databases to the new
server, would that recreate the entire state of the SQL Server installation?
Would I also need to rename the new server with the old server's name?Hi Laurence,
It might be helpful to check out :
http://vyaskn.tripod.com/moving_sql_server.htm
Nathan H. Omukwenyi, MVP [SQL Server]
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:OdQe7zm5GHA.3452@.TK2MSFTNGP05.phx.gbl...
>I need to move an entire SQL Server installation (databases, logins,
>replication, jobs, DTS etc) to a new physical server.
> What method requires the least manual intervention? Ideally I would like
> to not have to reenter user passwords, and the replication to pick up with
> the remote SQL Servers where it left off etc.
> If I restored master, distribution, msdb and all user databases to the new
> server, would that recreate the entire state of the SQL Server
> installation? Would I also need to rename the new server with the old
> server's name?
>|||I'd also recommend Vyas's reference for the general properties.
Replicationwise, you must have the same servername, or else you'll need to
script out the replication setup, change the references to the server name,
apply the scripts and then initialize the subscribers. If you can name the
new box with the netbios name of the old one before installing SQL Server
and restoring the databases, you should be fine. For this to work, you'll
need to stop replication and take the old server off the domain (or rename
it).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Thanks for both of your replies. I read the article and understand the
technique.
The only thing I am concerned about is where Vyas says "Install the exact
same version of Windows operating system on the new server.". My old server
is Windows 2000 and the new one is Windows 2003. Is it really critical that
the Windows versions are identical? What effect could the Windows version
have within SQL Server?
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23psVtas5GHA.3592@.TK2MSFTNGP05.phx.gbl...
> I'd also recommend Vyas's reference for the general properties.
> Replicationwise, you must have the same servername, or else you'll need to
> script out the replication setup, change the references to the server
> name, apply the scripts and then initialize the subscribers. If you can
> name the new box with the netbios name of the old one before installing
> SQL Server and restoring the databases, you should be fine. For this to
> work, you'll need to stop replication and take the old server off the
> domain (or rename it).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>|||My guess is that he is referring to memory/processor settings which are
restricted by the windows installation. These are partially configured in
the master database using sp_configure, and if you are restoring the master
database there'll be some dependency there. Alternatively, he might have
been referring to MS DTC (used in immediate updating subscribers for
replication) or windows firewall settings if these defaults are different on
different windows versions.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Monday, March 19, 2012
Moving SQL installation to a new Partition
Hello,
I have a SQL 2000 installation on a small partion that I would like to
move to a second larger partion on the same disk array array with the
config as follows:
d: full installation of prod and test instances with data and log files
100 GB
e: empty partion with 204 GB which I want to move the "whole thing"
Good! You've just done that and found that it does not work!
I don't think there is any. Rather I would look at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\Parameters
as the prime suspect.
Hm, that would indicate that a DLL or somesuch is missing rather than a
database file.
I have a SQL 2000 installation on a small partion that I would like to
move to a second larger partion on the same disk array array with the
config as follows:
d: full installation of prod and test instances with data and log files
100 GB
e: empty partion with 204 GB which I want to move the "whole thing"
I did an Xcopy of all files,permissions and attributes, checked for
errors, then I changed drive
letters and restarted. Only one instance came up (the other threw an
error of: MSSQL,,the system cannot find the file specified.
I realize that I could detatch the DB's and move them leaving the base
install on the old partition however I would like to simulate the loss
of the disk array and the restore to said array from a backup.
(ultimately I want to delete the 2 partitions and restore from tape to
a single 300GB d: partition)
I am trying to buy time and avoid a re-install of SQL untill I can get
a whole new platform.
I can work it out on my own if someone can point me in the right
direction. I suspect a registry entry to a disk id (partition)Marc C (mchang@.allosource.org) writes:
Quote:
Originally Posted by
Hello,
I have a SQL 2000 installation on a small partion that I would like to
move to a second larger partion on the same disk array array with the
config as follows:
d: full installation of prod and test instances with data and log files
100 GB
e: empty partion with 204 GB which I want to move the "whole thing"
>
I did an Xcopy of all files,permissions and attributes, checked for
errors, then I changed drive
letters and restarted. Only one instance came up (the other threw an
error of: MSSQL,,the system cannot find the file specified.
>
I realize that I could detatch the DB's and move them leaving the base
install on the old partition however I would like to simulate the loss
of the disk array and the restore to said array from a backup.
Good! You've just done that and found that it does not work!
OK, assuming that you had stopped SQL Server prior you started copying,
the operation as you described it, should work I think. But if there is
a file you missed a long the way there may be trouble.
But for restoring from backup... You can't really just back up the disk
drive as such, you need to use SQL Servers own BACKUP command, so that
backups are consistent. (Well, if you stop SQL Server before you start
the backup, you might get away with it, but normally you don't want to
do that.)
Quote:
Originally Posted by
I am trying to buy time and avoid a re-install of SQL untill I can get
a whole new platform.
I can work it out on my own if someone can point me in the right
direction. I suspect a registry entry to a disk id (partition)
I don't think there is any. Rather I would look at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\Parameters
as the prime suspect.
Exactly where do you get this error?
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thanks for your reply. I get the error on boot/startup. It's possible I
had a file open during the copy so the sql service cannot find a file
at startup. I will look into the logs for more detailed errors when I
try again during my next maintenance window. however the sql errorlog
shows no entries during that time span -so it's likely sql never
starts.
The only record of the failure was in the System Event log event id-
7000 Source- Service Control Manager with teh message The
MSSQL$Instancename service failer to start due to the following error:
the system cannot find the file specified.|||Marc C (mchang@.allosource.org) writes:
Quote:
Originally Posted by
Thanks for your reply. I get the error on boot/startup. It's possible I
had a file open during the copy so the sql service cannot find a file
at startup. I will look into the logs for more detailed errors when I
try again during my next maintenance window. however the sql errorlog
shows no entries during that time span -so it's likely sql never
starts.
Hm, that would indicate that a DLL or somesuch is missing rather than a
database file.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Wednesday, March 7, 2012
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)
>
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)
>
Subscribe to:
Posts (Atom)