August 26, 2013 at 6:21 am
Hi,
I use transactional replication for reporting purposes. Something weird happened last week Friday. We had to recreate the transact replication due to system changes - the new fuctionality had to be implemented with it's own replication upfront before the reporting side's replication could be added. I had to go through the whole setup again - no problem because it is fairly straight forward. What happened after this was: A secondary process utilises the replicated database to feed info to a downstream service provider. This secondary process transmits any changes via a storedproc. After the replication was configured - bear in mind I marked it for re-initialization - two tables seemed to be truncated in the replicated database for a fraction of a second and re-populated thereafter. My question is thus: Does the replicated database's tables get truncated prior to the population of them on the initial replication? I would gather this much. Any assistance in this regard would be appreciated.
Regards,
Gert.
Kindest Regards,
Gert van Deventer
August 27, 2013 at 10:29 pm
What replication does when table already exists at the subscriber is defined by you. You have options that include:
- drop and create the table and then load data
- truncate the table and load the data
- do nothing
When creating the publication, you can set these options either at the publication or the article level
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply