On 7/19/06, Mark Stanton <[EMAIL PROTECTED]> wrote:
Are you referring to the fact that the (eminent) posters appear to have entirely missed the point of my post and started talking about the minor details?
I was talking to Andy, not you.
Was my question really that difficult to read?
No, it just wasn't particularly interesting.There are dozens of solutions to maintaining two databases in synch from tighly-coupled database syncronization, through message processing systems like the MQ Series or Microsoft MSMQ to loosely-coupled ETL solutions. The choice depends on budget, aversion to risk, technology in use, the architecture of your current platforms (where's the web server, running what? In-house or hosted? What's the target database? What's the connectivity between the two?), the costs of losing a transaction, the budget, the budget, the budget, the timeline, the resources available, and so forth. SInce you didn't supply any of that information, there wasn't a lot to answer on your question. So we talked about what we could. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
