RE: Writing into Files from Stored Procedures

What about using ER ; it's free (builtin) and works quite happily with unreliable network connections (ie: it's queue-based replication) and it's pretty simple to implement. -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of marc.aurele.severus@gmail.com Sent: 05 May 2009 16:32 To: informix-list@iiug.org Subject: Re: Writing into Files from Stored Procedures > > There isn't any particularly easy way to do that. > > As Enrique suggested, if you aren't dealing with a temporary table, > you can use the SYSTEM statement to run, say, dbaccess and unload the > data that way.  It isn't very elegant; it won't be very fast.  And are > you sure you want to trigger this every time someone selects from the > table?  What do you envisage as the action that triggers your > triggered stored procedure? > I'd like to synchronise two very specific databases on two different servers. Network communication is not reliable, and network may sometimes be off. This synchronisation is a temporary solution (one or two weeks), so we cannot acquire an expensive software to do this. My idea : I put a trigger on INSERT, UPDATE, or DELETE statements in the first database. When someone inserts / updates / deletes data in the first database, the trigger exports the values into a file. When the network is available, the file is copied to the second server by FTP, and the second database is updated with the data. I guess there's probably a less dirty way to do this, but don't forget this is just a temporary solution. _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list