: )
excellent. i envy you.
i'd noticed the same thing about oracle. seems
to be a resource hog. the only thing worse that
i've seen is ms access. they make mysql look
very efficient.
hate to say much, since it appears that you know
what you're doing, but you might also take a look
at r
> i'm running an oracle enterprise server in a test
> environment for corereader, and i've noticed
> that, although oracle sometimes takes a while to
> wake up, after you have its attention, it throws
> data at you very fast. sometimes a developer
> does not use connections properly. in your case
t; And (I quote) If one uses sockets to connect to the MySQL server, the
> server will open and
> read the text file directly.
>
> As I said, these are ideas & I hope it will at least give you some ideas
> too...
>
> Cheers,
>
> Andrew
>
>
>
>
> -Original
since you're comfortable with rolling your own
tools, here are some observations about the ado
approach, and which could be applied to odbc as
well.
i'm running an oracle enterprise server in a test
environment for corereader, and i've noticed
that, although oracle sometimes takes a while to
--Original Message-
From: Wesley Brown [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 20 November 2002 20:24
To: Simon Windsor; [EMAIL PROTECTED]
Subject: RE: The dreaded move from Oracle to MySQL
Well, it looks like Simon has the best possible answer so far. I did a test
dump into a delimited file
> Can you explain this procedure to me a little better or point me to
> something I can read? I still have to convince the person who manages the
> Oracle box to open up an NFS share.
The point of using NFS to transfer the files from the oracle box to the
mysql box is to avoid copying the data twi
Well, it looks like Simon has the best possible answer so far. I did a test
dump into a delimited file from Oracle and imported that using the LOAD
command in mysql and sustaned about 11,000 inserts a second. This is with no
indexes on the mysql tables at all. I have also tried using the dbtools
im
Hi
I have moved huge amounts of data around in the past, from Oracle to Oracle,
and Oracle to MySQL.
The problems to consider are
- export speed
- load speed
It can take hours to download a large database, nevermind re-loading it into
another database. It is usually best to export the data in
Scott Pippin
[EMAIL PROTECTED]
>>> "Wesley Brown" <[EMAIL PROTECTED]> 11/20/02 11:24AM >>>
>Well, This is my first attempt at moving from Oracle to MySQL on such
a
>large scale and so far it isn't going well at all. We are running
oracle
>7.3.4.0.1 and MySQL 4.0.4-0 standard. We are moving 101 t
