Ronnie-
I often work with datafiles in size greater than 100GB, so please take that
into consideration of your needs — small datafiles might not need as extensive
an effort.
Based on my experience, I would highly recommend you use the sql export/sql
import routines — they are the most efficient, assuming there is no level of
data manipulation.
In the event there is any need for data manipulation (change in field
order/data types, update UUIDs, etc.), then your best bet will be to create a
generic series of routines that will allow you to monitor the export and import
routines on a table level basis.
HTH,
Mike
Mike Beatty
Objective Systems
>
> A client has requested to decommission a v13 database and merge the
> data into a separate v15 database.
> The 2 database structures started the same (as in same tables and fields) but
> has expanded in different directions down the years.
> It would be fair to say that the fields in the v13 structure would be a
> subset of the v15 structure.
>
> A send/receive record option would not be feasible.
> Tinkling with some ideas, perhaps exporting table data to CSV file (from v13)
> and import into v15.
> Or perhaps just exporting individual tables (individual) fields to text files
> with custom delimiters….
>
> What would be the best way to accomplish this?
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
