August 8, 2005 at 2:02 pm
We had a huge update to a published table, and when it tried to replicate to the subscriber, the log file filled up & the job bombed. I took a look in the subscriber table, and I see some records in the table from this weekend's job !?!? Shouldn't they have all been backed out when the job failed ??
Wassup with that ?
August 9, 2005 at 8:43 am
It looks like this shouldn't happen, according to BOL:
Transaction boundaries are preserved. If, for example, 100 rows are updated in a transaction, either the entire transaction with all 100 data modifications are accepted and propagated to Subscribers or none of them are.
But my guess would be when the log filled up and killed the Distribution Agent all bets are off.
In my experience distribution failures call for a new snapshot, I never spent any time trying to figure out exactly which records are wrong or missing.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply