Table replication...

Post Reply
Posts: 68
Joined: Mon Aug 28, 2006 4:43 pm

Table replication...

Post by tboyer »

I was wondering if you have any "best practices" advice for table replication. We want to mirror one of our main production tables so we don't have table contention between background processes and user interactions.

The tables are in the same database, so we're planning to write a vortex script to cron every 10-15 seconds and query for inserts/updates in the source table. If the previous instance is still running, the script will just stop. Any pitfalls to this that you see?


Posts: 1
Joined: Fri Sep 19, 2008 2:17 pm

Table replication...

Post by markawillson »

The separate process you propose is probably the best way to keep the mirroring isolated from the user. Things like triggers or manually updating both tables at the same time would tie mirroring to the user activity.

Make sure you have the index needed to make your check for recent activity fast.
Post Reply