First thing that comes to mind is an update trigger on the Unidata side that captures every write attempt. The trigger could compare the before and after versions of the record and execute a call to a SQL update process that you come up with. The trigger could normalize your data (or whatever you needed done) and could be added with no impact to your application.
Mike >From: "Kevin King" <[EMAIL PROTECTED]> >Reply-To: [email protected] >To: <[email protected]> >Subject: [U2] Replication Between Unidata and MySQL >Date: Fri, 28 Jul 2006 14:30:56 -0700 > >I have been assigned a unique project and have been given some pretty >stringent requirements. Basically the project involves a subset >replication of a Unidata database into MySQL. As certain records >change in Unidata (6.0) that record is to be flushed to a separate >server running MySQL. Off-hours batch updates are not an option at >this point, inconsistency between systems is intended to be momentary >at best. > >I can handle the conversion and flattening of the data; that's >certainly no deal breaker but keeping the MySQL server updated on a >near-realtime basis has me a bit freaked out. Has anyone handled this >kind of thing? Is there a connector to MySQL that can be addressed >from within Unidata? I could certainly do something with ODBC I would >figure but with Unidata running on AIX I'm not sure how exactly I'd >move the data to the MySQL server (running on a Win box) directly. > >Other options off the top of my head include > >* ...using a http server to update the MySQL instance and using the >callHttp interface or... >* ...writing a TCP listener to do the updating of the MySQL instance >and using Unidata sockets to move the data. > >However, these will necessitate a bit of code that I'd prefer to avoid. >What would you do? ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
