Given that you already have expertise in triggers, that would seem the
logical way to go. Just have the trigger write some indicator (as you
mentioned, a dataq) and then a background job can take it from there.
That way the job that issues the live db update isn't delayed by
replication. And then you can take down the replication and just have it
queue up as needed.
This thread ...
Re: Direction for Keeping Web DB up to date, (continued)
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact