No problem.  The schema of the target table(s) just have to be
compatible for the replicated columns, not identical.  The target tables
can contain additional columns like a DATETIME YEAR TO FRACTION(3)
column for the update time and even a source server column if you were
gathering data from multiple sources.

Art S. Kagel
Oninit

===========================================================================================
Please access the attached hyperlink for an important electronic communications disclaimer:

http://www.oninit.com/home/disclaimer.php

===========================================================================================

Luke,

We are using Replicate1 to replicate bi-directionally between Informix 10.00.FC4 and SQL Server 2005. What kind of locking issues are you having? We have been in production for over a year now and as long as the transaction sizes are small during the high OLTP hours we have had no issues.

BTW our Replicate1 Informix host is one node in a 3 node update anywhere ER environment. It's a little exciting to see that there's someone else out there using Rep1.

DL

----- Original Message ----
From: "Luke.Schollmeyer@gmail.com" <Luke.Schollmeyer@gmail.com>
To: informix-list@iiug.org
Sent: Thursday, January 24, 2008 11:10:11 AM
Subject: easy IDS Enterprise replication question

Hello,

I'm
new
to
managing
a
group
using
IDS,
and
am
familiar
with
other
RDMS
platforms,
but
just
not
up
to
speed
yet
on
this
particular
one.

We
have
a
two-fold
problem
getting
data
out
for
use
in
a
reporting/
data
warehouse
from
our
OLTP
environment.  
The
issue
is
that
we
do
not
have
last
update
date
and
time
columns
on
our
tables,
so
picking
up
the
data
deltas
from
the
last
time
the
ETL
process
ran
isn't
an
option.  
The
other
is
that
we're
using
a
trigger-based
replication
package
(Replicate1),
but
we're
experiencing
locking
issues
after
applying
the
replication
triggers
(we're
using
this
third-party
application
because
we're
pushing
to
DB2).

So,
while
we're
trying
to
figure
out
if
the
locking
can
be
remedied,
I
want
to
have
a
viable
Plan
B
by
having
an
additional  
instance
of
IDS
and
using
ER
to
replicate
to
it.  
Can
I
have
the
destination
tables
be
slightly
different
(having
an
extended
column
set
to
indicate
the
date
and
time
the
row
changed)
than
the
source
data?  
This
would
be
ideal
for
some
intra-day
reporting
needs
and
as
the
sourced
database
for
the
ETL
process
to
push
to
DB2.

Thanks
for
any
advice.

_______________________________________________
Informix-list
mailing
list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list