August 23, 2016 at 5:10 am
Hi,
When a new transactional snapshot is being applied when is @pre_creation_cmd put into action?
I've always assumed it's used per article and just before the article receives the new data. Thus leaving as much of the current data available for as long as possible so that other processes on the subscribers can continue.
But after a long night of applying a new snapshot (<8gigs) I noticed that some tables were empty and some had data. It's seems that @pre_creation_cmd is being called to start with, in my case dropping and recreating each article before data transfer starts.
By "Some had data" I mean, it was in the middle of the snapshot being applied and the subscriber does have extra tables.
So is it used per article, just before filling the table or are all articles dropped and recreated at the start of applying the snapshot?
Is Replication Monitor evil?
As mentioned, I had a long night of applying small snapshot. Shouldn't have taken even 15 minutes, but ended up taking hours.
Because it was the middle of the night and all subscribers had almost no activity, I can only assume the Replication Monitor was somehow holding things up.
Kendra Little[/url] mentions Replication Monitor blocking when it's used concurrently, but I was the only one online at the time and it is extremely unlikely that someone else happened to leave replication monitor open.
Replication links:
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply