Proposing three alternatives:
1) UniData Triggers that call a UniData EDA (Extended Data Architecture)
interface to write to MySQL. The only thing that has to be developed is
the MySQL interface for EDA. The burden here is adding triggers for the
UDT database. Hummm
2) UDT Triggers that feed
Steve O'Neal wrote:
Proposing three alternatives:
1) UniData Triggers that call a UniData EDA (Extended Data
Architecture) interface to write to MySQL. The only thing
that has
to be developed is the MySQL interface for EDA. The
burden here is
adding triggers for the UDT database. Hummm
EDA is not OFS. It is a new portion of UDT 7.x. In U2 Lab Services, we
try to push new technologies rather than driving the car with our hands on
the rear view mirror!
Man, stuck both feet in my mouth. OK. My Bad...
First foot... UDT 6.x does not have EDA. It was included in 7.x. Sorry.
EDA is not OFS. It is a new portion of UDT 7.x. In U2 Lab Services, we
try to push new technologies rather than driving the car with our hands on
the rear view mirror!
Just a thought. The new version of DB2 has a free version to compete with
and convert MYSQL users. If you converted the
DataStage Server edition does work with UniData. There is a UniData
passive stage in the same group with the UniVerse stage for access to
these files. Now, if you are planning on using the Hashed File stage,
1) that only works with UniVerse files; 2) is a very bad idea since
there is no
of the world, too expensive for the market size.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Clifton Oliver
Sent: Monday, 31 July 2006 3:01 p.m.
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Replication Between UniData and MySQL [ad]
DataStage Server
Of Tony Gravagno
Sent: Friday, July 28, 2006 8:33 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Replication Between Unidata and MySQL [ad]
Kevin, you can use triggers for the first part as Adrian suggests. As
always I'll recommend mv.NET to do the second part. When you put your
data
Kevin, you can use triggers for the first part as Adrian suggests. As
always I'll recommend mv.NET to do the second part. When you put your data
into a queue file, you can simultaneously log an action item into a queue
for mv.NET. This will tell a new external routine what to pick up from the
