Thanks to Angelo and Adrian for replies, probably going to use mv.net (core objects) with a Unidata trigger.
Regards Graham -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Merrall Sent: Thursday, November 09, 2006 8:12 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] RE: Unidata v6 into SQL 2005 Graham, > Next dilemma is how to get really time updates from Unidata into SQL. > I was thinking about adding a trigger to the Unidata file which > execute a SQL command to update the SQL database? > > Very grateful for any advice on how anyone else has achieved really > time updates from Unidata to another database. I'm not sure if anyone has achieved real time as opposed to near time. The problem with putting the update into a trigger is you are tying the SQL update to your regular transaction and potentially slowing it down as well as all the error handling and recovery issues (what to do when one system is down and your updates need to queue.). AFAIK A more common approach is to use the triggers to update a UDT file of updates to go to SQL and then have a phantom or cron poll this and process them. By working around timing etc., you should be able to get your lag pretty low. The cron process can use just about whatever transmission procedure you like. >From experience, make sure you have procedures to handle one or other servers being down, lost updates, clearing queues, regenerating messages, logging and status checking. It would be interesting to see where common consensus is at now as the above was the common practice a few years back when we set it up. Reviewing it is on my to-do list. HTH, Adrian ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
