:[EMAIL PROTECTED] On Behalf Of Kevin King
Sent: 29 July 2006 03:12
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Replication Between Unidata and MySQL
From: Of Mike Randall
Sent: Friday, July 28, 2006 5:46 PM
...The trigger could normalize your data (or whatever you
needed done
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
BTW - i have succesfully used the MySQL odbc drivers on unix to write to
MySQL on windows and unix machines using the unidata bci calls from my
databasic - it works very well .
One point to note - there was a bug in version 4 of the MyODBC drivers that
go with MySQL 4. The bug was to do with the
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
[EMAIL PROTECTED] wrote:
Good stuff Adrian. I've pretty much decided on Unidata triggers to
figure out what changed and write to a queue file and then have some
program pulling from that queue to flush to MySQL. But I was hoping
that I could do a lot of this in Unidata and I'm fearing I'm
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
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.
the
log by writing a lot of zeroes to a file (created for that purpose
logged) after x seconds, then ignore those zeroes at conversion...
From: Kevin King [EMAIL PROTECTED]
Reply-To: u2-users@listserver.u2ug.org
To: u2-users@listserver.u2ug.org
Subject: [U2] Replication Between Unidata
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan
Fitzgerald
Sent: Friday, July 28, 2006 3:09 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Replication Between Unidata and MySQL
Could you use transaction logging process the log file as soon as it
fills? You'd
Kevin,
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
Kevin,
I forgot to mention - you could look into the IBM MQseries support
added into Unidata but I don't think it was there at 6, you may need
to upgrade for this and hand IBM a lot of $ for the websphere mq
software.
Adrian
---
u2-users mailing list
u2-users@listserver.u2ug.org
To
]
[mailto:[EMAIL PROTECTED] On Behalf Of Adrian
Merrall
Sent: Friday, July 28, 2006 3:54 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Replication Between Unidata and MySQL
Kevin,
I have been assigned a unique project and have been given some
pretty
stringent requirements. Basically
you
needed done) and could be added with no impact to your application.
Mike
From: Kevin King [EMAIL PROTECTED]
Reply-To: u2-users@listserver.u2ug.org
To: u2-users@listserver.u2ug.org
Subject: [U2] Replication Between Unidata and MySQL
Date: Fri, 28 Jul 2006 14:30:56 -0700
I have been assigned
Subject: RE: [U2] Replication Between Unidata and MySQL
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
From: Of Mike Randall
Sent: Friday, July 28, 2006 5:46 PM
...The trigger could normalize your data (or whatever you
needed done) and could be added with no impact to your application.
I wouldn't say no impact per se but I think the trigger idea has
merit overall as a minimally invasive change
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
20 matches
Mail list logo
