Wednesday, March 28, 2012

OK now I'm confused re snapshots in transactional

OK, yesterday I was asking about regular snapshots, and Hilary
explained that the snapshot agent looks to see if one is needed and
generates one as necessary. Well, I have another couple of questions
about that, but let's pass on them for the moment and ask something
else.
When setting up replication, if I do manually create a new subscriber
by restoring a 100% current backup, and tell the wizard that the
subscriber has schema and data, then effectively the snapshot agent
runs and does absolutely nothing, right? Or does it not even run, the
transactional replication just cranks right up?
For extra credit, what if the backup is 99.999% current, but lacks an
hour or so of transactions, is there anything in the replication setup
that is smart enough to figure this out and fix it?
Joshua Stern
ps - is this addressed in detail in Hilary's book?
Joshua,
in the case of transactional replication, the snapshot agent won't do
anything. This means that you'll need to create the correct stored
procedures on the subscriber using sp_scriptpublicationcustomprocs.
At the time of adding the subscriber it is assumed that the subscriber is up
to date. If you have done a manual initialization, you'll need to prevent
users editing data until the subscription is added.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

No comments:

Post a Comment