Moving subscriber to a new server

Hi,
environment:
SQL Server 2000 EE, SP4, latest security update on win 2003. Using merge PULL
replication.one Publisher, 2 subscribers.
We have a need to move a DB with a pull subscription to a new
server. The new server will be setup on the same network with the same name as
the old one. (publisher on a different network)
after moving the database (detach,attach ,subscriptiom need to be deleted to
do this) and if the publisher has new data inserted during the move how can I
get the subscriber on the new server to synch with publisher and get the data
changes.
CTS DBA
hey can anybody please help?
I got till this Monday only to come up with the solution
CTS DBA
"CTS_DBA" wrote:

> Hi,
> environment:
> SQL Server 2000 EE, SP4, latest security update on win 2003. Using merge PULL
> replication.one Publisher, 2 subscribers.
> We have a need to move a DB with a pull subscription to a new
> server. The new server will be setup on the same network with the same name as
> the old one. (publisher on a different network)
> after moving the database (detach,attach ,subscriptiom need to be deleted to
> do this) and if the publisher has new data inserted during the move how can I
> get the subscriber on the new server to synch with publisher and get the data
> changes.
> --
> CTS DBA
|||Have a look at @.allow_subscription_copy which is a property of the
publication. It can be set to allow copying of subscriber databases. Can't
test your particular requirements at the moment, but please give it a go.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||thanks paul,
copying subscription works for dbs less than 2GB, mine is 12Gb.
I'm still testing this but looks like it's working,
synch the subscriber with the publication,
run the snapshot agant
make a copy of the db and move it to the new server
create a new subscription.
the new subscription will captures changes since the last back up
any body has any commnets?
"Paul Ibison" wrote:

> Have a look at @.allow_subscription_copy which is a property of the
> publication. It can be set to allow copying of subscriber databases. Can't
> test your particular requirements at the moment, but please give it a go.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>

Moving Published db to different server (cannot reinitialize)

When I've talked about nosync initialization, this was
connected with subscribers. When moving the publisher to
another server of a different name I have always scripted
out the publication, edited it to alter the servernames
then run the script on the new publisher and
reinitialized. If the tables are large, you could
compress the BCP files (winzip9.0) with an alternative
snapshot location being used for the subscription, or
DVDs etc. BTW we have a 35GB database, 20GB of which is
snapshotted occasionally and using fileshares the whole
process takes 2 hours or so.
HTH,
Paul Ibison
In article <18a501c4dd44$b0da7d00
$a501280a@.phx.gbl>, Paul.Ibison@.Pygmalion.Com
says...
> When I've talked about nosync initialization, this was
> connected with subscribers. When moving the publisher to
> another server of a different name I have always scripted
> out the publication, edited it to alter the servernames
> then run the script on the new publisher and
> reinitialized. If the tables are large, you could
> compress the BCP files (winzip9.0) with an alternative
> snapshot location being used for the subscription, or
> DVDs etc. BTW we have a 35GB database, 20GB of which is
> snapshotted occasionally and using fileshares the whole
> process takes 2 hours or so.
> HTH,
> Paul Ibison
>
how long does it take to distribute that snapshot
to a wan subscriber?
Ok on the compression part. Basically I've run
into where windows wont compress a bcp file over
2gb. I guess that is why you are saying use
winzip or rar. Do a normal snapshot to an
alternate location. Then compress those bcp
files, send those compressed bcp files over the
wan link to the subscriber. They unzip them and
insert that information. They I would "push the
new subscription" at that point? How do i keep
the distribution agent from trying to push the
original snapshot that was made , and only push
the data that is in the log reader?
I guess I could move the snapshot files so it
will just move on to the data that is in the log
reader?
Thanks for the help on this paul.
-comb