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