Re: SQL replication

On Fri, 5 Aug 2005 09:13:01 +0100, "Paul Ibison"
<Paul.Ibison@xxxxxxxxxxxxx> wrote:

>Josh,
>it all depends what you mean by 'Start replication'. After the restore of
>the backup there will be no subscription info for that subscriber, so it
>needs setting up. Doing a normal setup will simply overwrite all the
>articles and you're in the same situation as having created an empty
>database. Chris' link refers to nosync initializations, which is one
>posibility, but this requires a fair amount of manual interaction in the
>case of transactional replication, adding new articles automatically must be
>done using scripts and special care must be taken with identities (see
>http://www.replicationanswers.com/NoSyncInitializations.asp). I think
>attachable subscription databases is by far the easiest solution :)

Paul,

Yes, I could be clearer.

For one thing, I do basically assume that one abandons all the
wizardly control of replication and does everything by manually tuned
scripts.

After I posted, it occurred to me that, with some care, the latency I
suggest which includes kicking people off both systems, can be
minimized, along the lines you mention. One could:

(a) Start with your operational database before it becomes a
publisher.
(b) By hook or crook, establish the suscriber and get replication
going, develop all the proper scripts.
(c) When it is time to deploy it for real:

* Replication is already running from publisher to subscriber, but it
is not fully in sync, may even be stopped, with updates queueing up
waiting to be resolved and delivered.
* Kick all users off publisher.
* Take backup.
* fail the distribution process so the updates queue up
**** now, let users back on publisher, and let the updates queue up,
shorter period of latency on the publisher!
* restore the backup on subscriber
* apply new scripts as necessary to publisher/subscriber (nosync),
turning on replication
* maybe give it a few minutes to catch up
* let users back on subscriber

Josh

.

Relevant Pages

  • Re: Transactional Replication 2005
    ... replication from production database as the publisher and subscribe it to ... Create the distributor on the publisher server ... I then create the subscriber, ... the identity NFR property setting has to match between publisher ...
    (microsoft.public.sqlserver.replication)
  • Re: Sp_adjustpublisheridentityrange and resetting identity range
    ... > identity ranges you have set on your publisher. ... > ranges which will work for the lifetime of their replication solution. ... > should apply this value on the subscriber. ... >> restored the published database from a backup. ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge Repl Failure - Rollback or not
    ... Looking for a SQL Server replication book? ... > Publisher box now shipped to new location. ... > Generate a single insert at subscriber and replicate. ... > Disconnecting from Subscriber 'GENDEV003' ...
    (microsoft.public.sqlserver.replication)
  • RE: Replication problems over WAN
    ... I suggest using a backup to init your subscriber. ... Setup subscriber in log shipping, or if you can get a full ... We have tried several methods to get transactional replication to work. ...
    (microsoft.public.sqlserver.replication)
  • Re: Disaster Recovery for Bi-Directional Transactional Replication
    ... With un-directional replication you can have multiple publishers publishing ... If the main publisher went off line a standby publisher could go online and ... subscriber, and then you would be faced with the same question as to what ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)