Replication concept question

  • We have a server that has been loaded with historical data, and now has live data added via transactional replication (from a live only server) every 10 minutes. The website in theory is up 24/7 but generally there is no activity between 11pm and 6am.

    The trouble is, every now and then there IS random activity - and I need to take the replication down once a week for data archiving (to prevent the archiving leading off to 8 other replicated servers).

    My question is - what would you guys do/use to check for and catch up with the few records that may be missed (via 10 articles) in the 1 hour that the subscription is removed? At the moment I run a manual data examiner third party tool, but I need to automate it ideally. Snapshots and sync are out of the question due to the speed of the line and the ridiculous amount of tables.

    Be interested to see what other people do to deal with such situations. I guess using linked tables I could check using some sql and then a bcp maybe.

  • just replied on one of the post today, so will advice the same here...

    there is tool tablediff utility which will compare 2 tables and will show the difference.

    ----------
    Ashish

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply