moving replication to new servers

I've got a publisher, distributor and subscriber on different servers and I
want to move all 3 to different servers. Is there a way to restore the
publishing database
on the new publisher, the subscribing database on the new subscriber and
then continue replication? knowing, of course, that I'd have to set up the
new distributor as well.
I know I can create the new publication, backup the database and restore
that on the new subscriber and initialize replication backup, but the
databases are fairly large and if I can restore both the publisher and the
subscriber at the same time, it would save much time. I need to minimize
down time.
Thanks!
There is no real way to do this. What Microsoft does support is restoring
master, distribution, msdb, and the publication database on a new server,
restoring the last tlog of the publication database on the new server with
the keep_replication switch, taking the first server offline, rebooting the
standby after renaming it as the original publisher name, and then issuing a
sp_replrestart to get everything working again.
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
"Steve" <Steve.sam@.hotmail.com> wrote in message
news:eb2nTSzaHHA.2448@.TK2MSFTNGP02.phx.gbl...
> I've got a publisher, distributor and subscriber on different servers and
> I want to move all 3 to different servers. Is there a way to restore the
> publishing database
> on the new publisher, the subscribing database on the new subscriber and
> then continue replication? knowing, of course, that I'd have to set up
> the new distributor as well.
> I know I can create the new publication, backup the database and restore
> that on the new subscriber and initialize replication backup, but the
> databases are fairly large and if I can restore both the publisher and the
> subscriber at the same time, it would save much time. I need to minimize
> down time.
> Thanks!
>

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

Moving projects from server to workstation issue.

Dear folks,

I’ve moved my server folder which contains about 10 dtsx and its ADO .net connection as well as OLEDB into my folder workstation. Then, when I’m gonna to open them appears this error:

Error1Error loading M_HAC_Modelo198_CECA.dtsx: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Clave no válida para utilizar en el estado especificado.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.c:\ssis\hacienda_anual\M_HAC_Modelo198_CECA.dtsx11

Translate into english: "Clave no válida para utilizar en el estado especificado" = Invalid key for to use in the specified state (more or less)

What really happen? Well, I wrote these packages using a domain user (belong to Administrators group in Active Directory) via Terminal Server and now I want to modify them by mean my domain user (I already have got installed sql25k client tools and the stuff required)

I thouht that these connections were saved in the same folder where dtsx, dtsproj, etc..

Solution? Create them again? I hope that it will be a piece of cake otherwise...

Thanks in advance for any though or advice,

Well, it really occurs with a only dtsx. Issue raises with a SSIS packages which it was a importation of a sql2k dts. So that it's add a little bit of confusion. Others ones are fine.

Moving Master, Msdb and Model

I've seen the articles about restoring from backup for
the above. But how do you move these databases to a
different location/drive? Thanks.
INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/default...;EN-US;q224071
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"GoMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d94401c4548c$833ffd20$a601280a@.phx.gbl...
> I've seen the articles about restoring from backup for
> the above. But how do you move these databases to a
> different location/drive? Thanks.
|||This article should be helpful:
http://support.microsoft.com/default...b;en-us;224071
Russell Fields
"GoMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d94401c4548c$833ffd20$a601280a@.phx.gbl...
> I've seen the articles about restoring from backup for
> the above. But how do you move these databases to a
> different location/drive? Thanks.