Moving a replicated database

How best to move a replicated database? I have a situation where the
customer's data is currently being replicated (merge), but I need to move
the database to another machine -- without breaking replication. I'm
thinking, script out the database, then export the data. Then run the script
to re-create, import the data, then set up replication on the new machine.
Anyone have a better solution?
On a related point, don't the subscribers then become orphans? The on-board
changes (PocketPCs) still must talk back to the original publisher.
Earl,
moving a publisher to a new server really involves reinitialization.
However, if the data is all synced up, you could do a nosync initialization.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||How can a no sync initialization be done? I didn't see it as an option in the
menu after the right click on the publication.
-A
"Paul Ibison" wrote:

> Earl,
> moving a publisher to a new server really involves reinitialization.
> However, if the data is all synced up, you could do a nosync initialization.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Adam,
here you go... http://www.replicationanswers.com/No...alizations.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)