; < [EMAIL PROTECTED] >
To: mysql@lists.mysql.com
Sent: Monday, July 23, 2007 1:44:53 PM (GMT-0500) America/New_York
Subject: performance of extended insert vs. load data
all,
I need to migrate ~12GB of data from an Oracle 10 database to a MySQL
5.0one in as short a window as practically
-0500) America/New_York
> Subject: performance of extended insert vs. load data
>
> all,
>
> I need to migrate ~12GB of data from an Oracle 10 database to a MySQL
> 5.0one in as short a window as practically possible (throw tablespace
> in r/o,
> migrate data & repoint w
On 7/23/07, mos <[EMAIL PROTECTED]> wrote:
Load data will of course be much faster. However to obtain the maximum
speed you need to load the data to an empty table, because then MySQL will
load the data without updating the index for every row that's added, and
will instead rebuild the index only
At 11:44 AM 7/23/2007, Sid Lane wrote:
all,
I need to migrate ~12GB of data from an Oracle 10 database to a MySQL
5.0one in as short a window as practically possible (throw tablespace
in r/o,
migrate data & repoint web servers - every minute counts).
the two approaches I am considering are:
1.
.mysql.com
Sent: Monday, July 23, 2007 1:44:53 PM (GMT-0500) America/New_York
Subject: performance of extended insert vs. load data
all,
I need to migrate ~12GB of data from an Oracle 10 database to a MySQL
5.0one in as short a window as practically possible (throw tablespace
in r/o,
migrat
On 7/23/07, Sid Lane <[EMAIL PROTECTED]> wrote:
is either one significantly faster than the other?
Yes, LOAD DATA INFILE is much faster.
are there additional (faster) approaches I have not thought of?
Not that I've found. I think you'd have to write directly to the C
API to beat LOAD DATA
all,
I need to migrate ~12GB of data from an Oracle 10 database to a MySQL
5.0one in as short a window as practically possible (throw tablespace
in r/o,
migrate data & repoint web servers - every minute counts).
the two approaches I am considering are:
1. write a program that outputs the Oracl
