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?
Thanks,
Tom
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?
Thanks,
Tom