thorough.
Luc
Regards,
Harrison
On Tuesday, August 3, 2004, at 10:23 AM, Luc Charland wrote:
We are evaluating the replacement of a Sybase database with MySQL.
The databases are 60+GB, containing more than 100 tables.
Since we need transactions, that implies InnoDB. We were happy with
the early resu
[EMAIL PROTECTED] wrote:
Estimado Luc,
Con fecha jueves 5 de agosto de 2004, 11.07.23, escribió:
Did you try disable index table? When you import millon of records
there is an overload indexing it. First import and then create your
index or:
ALTER TABLE tb_name DISABLE KEYS;
import data...
ALTER
s for example.
The speeds up the whole thing a lot because there is no need for a
disk flush after every record insert.
"commit" means "the data are on disk for sure now
(or after a few seconds (if you set innodb_flush_log_at_trx_commit to
0 or 2 instead of 1))".
Regards,
any change,
but I don't expect it.
Luc
-Original Message-
From: Luc Charland [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 03, 2004 7:54 PM
To: [EMAIL PROTECTED]
Subject: Insert problems with InnoDB (big table)
We are evaluating the replacement of a Sybase database with MySQL
price on smalltest (price)"
"create index smallcost on smalltest (cost)"
"create index smallname on smalltest (name)"
______
Thanks for any help.
Luc Charland
--
MySQL General Mailing List
For list archives: http://lists.mysql.c
