Hi everyone,
I am hoping to get help with extremely slow performance of MyISAM to
InnoDB conversion. Or find out if this type of performance is usual
I have MyISAM table that contains - 3,299,509 rows and I am trying to
convert it to InnoDB for the use with row-level locking, and I am
getting
-
From: Mikhail Berman [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Wednesday, November 1, 2006 10:31:13 AM GMT-0500 US/Eastern
Subject: MyISAM to InnoDB conversion help
Hi everyone,
I am hoping to get help with extremely slow performance of MyISAM to
InnoDB conversion. Or find out
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 01, 2006 11:05 AM
To: Mikhail Berman
Cc: mysql@lists.mysql.com
Subject: Re: MyISAM to InnoDB conversion help
If you are do this in MySQL 5, try this:
ALTER TABLE table-name ENGINE = InnoDB;
That's all.
Let MySQL worry about conversion.
You may
-0500 US/Eastern
Subject: RE: MyISAM to InnoDB conversion help
Hi Rolando,
Thank you for your help.
I am on MySQL 5, and I have tried to do the conversion using ALTER TABLE
command. With the same very slow result.
Do you by any chance have specific suggestions how to tweak variables
related
Edwards [EMAIL PROTECTED]
To: Mikhail Berman [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Sent: Wednesday, November 1, 2006 11:24:00 AM GMT-0500 US/Eastern
Subject: Re: MyISAM to InnoDB conversion help
Check these variable
bulk_insert_buffer_size (Default usually 8M)
innodb_buffer_pool_size (Default
Great,
Thank you for your help Rolando,
Mikhail Berman
-Original Message-
From: Rolando Edwards [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 01, 2006 11:41 AM
Cc: mysql@lists.mysql.com; Mikhail Berman
Subject: Re: MyISAM to InnoDB conversion help
I just noticed your
A,
- Original Message -
From: A Z [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Tuesday, February 01, 2005 2:14 PM
Subject: Premature InnoDB conversion.
MySql 4.0.14
We tried to convert MyISAM table format to INNODB
format, it took forever to finish the process, someone
MySql 4.0.14
We tried to convert MyISAM table format to INNODB
format, it took forever to finish the process, someone
intervened and killed the process through Task
Manager.
Now can't run Mysqld-nt, running it with the --console
reports the followings. Your help is appreciated.
Microsoft
Hi. I have a query that has been running for 10.7 hours. It is converting a 3.6GB
MyISAM to Innodb.
38448 | copy to tmp table | alter table `MESSAGES` type=innodb
The innodb data file has increased 8.6GB in size since the command started.
How do I tell how far through the conversion the
Dear sir,
I am using MySQL database
I just wanted to use transaction.so as per manual i
have to make table type as Innodb.
Then i had set Innodb startup options as follows
innodb_data_file_path = ibdata1:2000M;ibdata2:2000M
innodb_data_home_dir = c:\ibdata
set-variable =
Hi Nilesh,
On Thu, 2002-02-21 at 15:14, Nilesh Deshpande wrote:
I am using MySQL database
I just wanted to use transaction.so as per manual i
have to make table type as Innodb.
Then i had set Innodb startup options as follows
innodb_data_file_path = ibdata1:2000M;ibdata2:2000M
At 21:14 20/02/2002 -0800, Nilesh Deshpande wrote:
Hi!
Very strange the printed messages you sent.
What MySQL release version are you using ? I did the test with
your start InnoDB set with 3.23.48 and got:
c:\mysql\binmysqld-max --standalone --console
InnoDB: The first specified data file
At 21:14 20/02/2002 -0800, Nilesh Deshpande wrote:
Hi,
Now I assume that the text you sent is from our documentation.
For to build an InnoDB table:
mysql create table table_name (id int)type=innodb;
Query OK, 0 rows affected (0.14 sec)
Regards,
Miguel
Dear sir,
I am using MySQL database
I
13 matches
Mail list logo
