Actually, our method currently goes 1 way, but we'll be expanding it to run back and forth.
When we logged the instructions, we also update a 'modified_datetime' column or a 'created_datetime' column. When the updates happen, they're compared to decide which value has precedent. As for the quickness of the system, its actually faster than the original version which included zipped data uploads. Cheers, Kevin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: July 19, 2005 10:47 AM To: CF-Talk Subject: RE: Syncing 2 different databases Thanks Kevin. Just so I'm clear...it sounds like you stored up data changes (e.g. update this field to the new value) as instructions in an xml document. During sync your web service performed the data changes as specified in the xml doc. 1. Did you do this both ways? Ie changes from system 1 performed on system 2, system 2 changes performed on system 1? What did you do about an older record trying to update a newer record? 2. Did you find this solution was robust? If not what problems did you encounter? Lorne -----Original Message----- From: Kevin Aebig [mailto:[EMAIL PROTECTED] Sent: July 19, 2005 09:23 To: CF-Talk Subject: RE: Syncing 2 different databases Well actually, I had to do something very similar... Instead of separating the calls into multiple webservice calls, we created 1 webservice that would interpret and parse an xml doc that contained instructions. If you're going to be doing mostly updates to the data and not inserts, than this would probably suit you as well. This kept the number of webservice transactions to a minimum and keeps everything running smoothly. Aside from using SSL, we also used shared key credentials to keep the initial handshake secure... Cheers, Kevin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: July 19, 2005 9:57 AM To: CF-Talk Subject: Syncing 2 different databases I have to sync code tables on 2 different databases (Oracle and SQLserver) belonging to 2 different companies. New codes or changes to existing codes might happen in either database. The only connection between the 2 networks is over the internet so I'd like the solution to be via web services. Most of the code tables only have a few hundred records but will need to be synced several times a day. Does anyone have any clever thoughts on the best way to do this? Lorne ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:212229 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
