moving to a new server

I need to move my Production SQL box to a new box, in a new domain, with a
new name for the box itself. Can someone point me to a white paper for this?
I've done alot of stuff similar to this, but theres enough differences here
make me nervous.
SQL2K SP3
TIA, ChrisR
What all do you need to move? User databases are easy. Are you just moving
the box an upgrading it or are you moving the entire installation? Is this
a stand-alone server or a SQL Server Fail Over cluster?
Sincerely,
Anthony Thomas

"ChrisR" <bla@.noemail.com> wrote in message
news:OSZNAbW4EHA.1188@.tk2msftngp13.phx.gbl...
I need to move my Production SQL box to a new box, in a new domain, with a
new name for the box itself. Can someone point me to a white paper for this?
I've done alot of stuff similar to this, but theres enough differences here
make me nervous.
SQL2K SP3
TIA, ChrisR
|||Everything is being moved. All system and User db's. I've done all of it in
the past but not to a new domain, new box name, etc. No its not clustered.
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
news:uEXcRAY4EHA.1300@.TK2MSFTNGP14.phx.gbl...
> What all do you need to move? User databases are easy. Are you just
moving
> the box an upgrading it or are you moving the entire installation? Is
this
> a stand-alone server or a SQL Server Fail Over cluster?
> Sincerely,
> Anthony Thomas
>
> --
> "ChrisR" <bla@.noemail.com> wrote in message
> news:OSZNAbW4EHA.1188@.tk2msftngp13.phx.gbl...
> I need to move my Production SQL box to a new box, in a new domain, with a
> new name for the box itself. Can someone point me to a white paper for
this?
> I've done alot of stuff similar to this, but theres enough differences
here
> make me nervous.
> --
> SQL2K SP3
> TIA, ChrisR
>
|||Moving user databases is easy, just detach and reattach. For the system
databases, make sure the new install is running the same version, edition,
and service pack and hotfix patch levels. At that point, you can just
replace the system databases with copies of the old.
To handle the new domain/computer name, SQL Server will automatically assume
the name of the server it is running on. If this is a named instance, this
can be a little trickier. Nevertheless, for linked servers and replication,
the master database also knows what server it is running on. You will have
to change that after you have moved master to the new host.
sp_dropserver <old_name>
sp_addserver <new_name>, local
Sincerely,
Anthony Thomas

"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%238s9JPY4EHA.1404@.TK2MSFTNGP11.phx.gbl...
Everything is being moved. All system and User db's. I've done all of it in
the past but not to a new domain, new box name, etc. No its not clustered.
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
news:uEXcRAY4EHA.1300@.TK2MSFTNGP14.phx.gbl...
> What all do you need to move? User databases are easy. Are you just
moving
> the box an upgrading it or are you moving the entire installation? Is
this
> a stand-alone server or a SQL Server Fail Over cluster?
> Sincerely,
> Anthony Thomas
>
> --
> "ChrisR" <bla@.noemail.com> wrote in message
> news:OSZNAbW4EHA.1188@.tk2msftngp13.phx.gbl...
> I need to move my Production SQL box to a new box, in a new domain, with a
> new name for the box itself. Can someone point me to a white paper for
this?
> I've done alot of stuff similar to this, but theres enough differences
here
> make me nervous.
> --
> SQL2K SP3
> TIA, ChrisR
>
|||I hope this will help as a reference (from Andrew J. Kelly):
http://www.support.microsoft.com/?id=314546 ; Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 ; Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 ; Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 ; How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 ; Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp ; Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 ; User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 ; How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 ; Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=274463 ; Copy DB Wizard issues
Sasan Saidi
MSc. CS, MCSE 4, Certified IBM MQ Administrator
Senior DBA
Brascan Business Services
"ChrisR" wrote:

> I need to move my Production SQL box to a new box, in a new domain, with a
> new name for the box itself. Can someone point me to a white paper for this?
> I've done alot of stuff similar to this, but theres enough differences here
> make me nervous.
> --
> SQL2K SP3
> TIA, ChrisR
>
>
|||Perfect! Thanks.
"Sasan Saidi" <SasanSaidi@.discussions.microsoft.com> wrote in message
news:B400D908-0407-4925-BAD1-3493A1E6A8DB@.microsoft.com...
> I hope this will help as a reference (from Andrew J. Kelly):
> http://www.support.microsoft.com/?id=314546 ; Moving DB's between
Servers
> http://www.support.microsoft.com/?id=224071 ; Moving SQL Server
Databases
> to a New Location with Detach/Attach
> http://support.microsoft.com/?id=221465 ; Using WITH MOVE in a
> Restore
> http://www.support.microsoft.com/?id=246133 ; How To Transfer Logins
and
> Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=298897 ; Mapping Logins & SIDs
after a
> Restore
> http://www.dbmaint.com/SyncSqlLogins.asp ; Utility to map logins to
> users
> http://www.support.microsoft.com/?id=168001 ; User Logon and/or
Permission
> Errors After Restoring Dump
> http://www.support.microsoft.com/?id=240872 ; How to Resolve Permission
> Issues When a Database Is Moved Between SQL Servers
> http://www.sqlservercentral.com/scri...p?scriptid=599
> Restoring a .mdf
> http://www.support.microsoft.com/?id=307775 ; Disaster Recovery Articles
> for SQL Server
> http://www.support.microsoft.com/?id=274463 ; Copy DB Wizard
issues[vbcol=seagreen]
> Sasan Saidi
> MSc. CS, MCSE 4, Certified IBM MQ Administrator
> Senior DBA
> Brascan Business Services
>
> "ChrisR" wrote:
a[vbcol=seagreen]
this?[vbcol=seagreen]
here[vbcol=seagreen]

Moving Replication Distributor to new cluster

Hi
What are the gotchas on moving a Replication Distributor to new hardware/a
new cluster?
Kind Regards,
T. Hagen
You have to drop the publications and disable replication on the publisher
before the move. You have to make sure your remote distributor is
clustered - which it appears to be
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"thagen" <thagen@.discussions.microsoft.com> wrote in message
news:23A725E7-ED77-4BD6-A8A6-AF3D91C96D2D@.microsoft.com...
> Hi
> What are the gotchas on moving a Replication Distributor to new hardware/a
> new cluster?
> Kind Regards,
> T. Hagen
|||As well as Hilary's response, and it's a long time since I worked on
clustering a distributor, I recall that the distribution working folder
should be set up as a shared resource on the cluster.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Thanks Hilary.
There is nothing to be done on the Subscriber side?
And as for the actual steps in moving the Distributor, you have any how-to
on that?
Kind Regards,
Torkild
"Hilary Cotter" wrote:

> You have to drop the publications and disable replication on the publisher
> before the move. You have to make sure your remote distributor is
> clustered - which it appears to be
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "thagen" <thagen@.discussions.microsoft.com> wrote in message
> news:23A725E7-ED77-4BD6-A8A6-AF3D91C96D2D@.microsoft.com...
>
>
|||Perhaps you mean the snapshot share While you can park this anywhere, it
is best on the publisher.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uRXwYO8ZHHA.2316@.TK2MSFTNGP04.phx.gbl...
> As well as Hilary's response, and it's a long time since I worked on
> clustering a distributor, I recall that the distribution working folder
> should be set up as a shared resource on the cluster.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
|||You can't move the distributor. You have to disable publishing on the
publisher. Pre-create the distributor on the remote distributor and then
configure your publishers to use this distributor. Then connect to your
publishers and enable replication, and enable it to use the remote
distributor. You will need to configure an administrative link password.
There is a guide in the sample chapter of my book.
http://www.nwsu.com/lowres_replication_ch02.pdf
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"thagen" <thagen@.discussions.microsoft.com> wrote in message
news:3B9C0EF4-E09C-455B-8F5B-9AC1B80BE7D9@.microsoft.com...[vbcol=seagreen]
> Thanks Hilary.
> There is nothing to be done on the Subscriber side?
> And as for the actual steps in moving the Distributor, you have any how-to
> on that?
> Kind Regards,
> Torkild
> "Hilary Cotter" wrote:
|||Yes -thanks for the correction Hilary (snapshot share).
It still makes sense to me though that this should be a shared resource on
the central (shared) array rather than a local node so it can fail over.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com