SQL Server Performance

Polling changes on a db, and copying changes to another db

Discussion in 'SQL Server 2005 Performance Tuning for DBAs' started by thebends, Apr 3, 2008.

  1. thebends New Member

    Hi all, I'm in the process of cleaning up a very VERY poorlyimplemented system. One of the problems I'm tackling consists of :

    1 - Database A
    2 - Database B (different schema than A)
    3 - A task which regularly polls A, checks for updated/new records and inserts them (with some transformation) into B

    As you can imagine, the overhead of the polling is killing the system. What I want to know is :

    What is the best way for A to notify B whenever there are changes to a particular table on A ?

    I'm running 2000 but we will most probably upgrade to 2005.

    thanks in advance to everybody
  2. Luis Martin Moderator

    What about a trigger in A?
  3. MohammedU New Member

    Is there any specific reason to copy the changes to another db on the same server?
    Check the replication opiton for this.

Share This Page