Results 1 to 2 of 2
  1. #1
    Join Date
    Apr 2008

    Question Unanswered: Replicating only one table, what's the best approach ?

    I have a single table on database A that needs to be replicated to two databases B and C in as-near-to-real-time as possible. The table is cleared every morning, and receives about 40,000 records per hour. Records are only added to the table, never updated or deleted.

    I'm wondering what is the best approach to replicate this table :

    1 - Transactional Replication
    2 - A trigger on the INSERT on table in A that then inserts the record into B and C
    3 - Timed jobs running on B and C that pull new records from A

    thanks all in advance.
    Last edited by thebends; 04-06-08 at 18:00.

  2. #2
    Join Date
    Nov 2004
    on the wrong server
    Provided Answers: 6
    I would go with number one. Transactional replication with immediate updating. The other 2 seem more prone to f*ck up and this is what replication was designed to do, so why would you want to roll your own when MS has provided you with such grand bells and whistles already?
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts