-----Original Message-----
From: owner-informix-list@iiug.org [mailtowner-informix-list@iiug.org]
On Behalf Of David E. Grove
Sent: 19 April 2005 09:18 PM

"Dirk Moolman" <DirkM@mxgroup.co.za> wrote in message
news:1113916359.f5c9344bed508aacf59a9907985ce0e2@t eranews...
>
> Are you doing this with transaction logging enabled ?
>
> You can create the schema, disable transaction logging, and populate
> your tables using table-to-table insert scripts.
> (also remember to disable indexes, constraints, etc.)
>
>
>Just to make sure I'm understanding you... You mean make the schema on
the
>new machine (say, with dbschema). Then, write a script that, table by
>table, does "INSERT INTO <table-in-new-database>... SELECT... FROM
><table-in-old-database>..." ?
>
>I'm thinking it might take a while. Mightn't we have problems from old
>tables being updated while script is running? What I mean is we might
not
>get a consistent state of the database transferred to the new system???
I
>may be misinterpreting or misunderstanding.


Note that you still need downtime on both machines (no active
connections) - so that you can keep your system consistent.

Downtime -> transfer from old to new -> go live on new


And the speed depends on how big your database is. This is just an
option, and you will have to decide which one you are comfortable with.


Regards
Dirk

sending to informix-list