D]>
To:
Sent: Tuesday, July 25, 2006 11:51 PM
Subject: Re: Row count discrepancy when converting from MyISAM to InnoDB
On Jul 25, 2006, at 11:55 AM, Frank wrote:
Why is the record count so low after conversion to InnoDB?
Who should I believe: InnoDB or MyISAM?
Any ideas as to what can be d
nt: Tuesday, July 25, 2006 11:51 PM
Subject: Re: Row count discrepancy when converting from MyISAM to InnoDB
On Jul 25, 2006, at 11:55 AM, Frank wrote:
Why is the record count so low after conversion to InnoDB?
Who should I believe: InnoDB or MyISAM?
Any ideas as to what can be done to avoid loss of
Thank you to everyone who replied. It turned out I had index corruption and
after running an OPTIMIZE TABLE I was able to convert all the records to
InnoDB.
Thanks,
Frank
On Jul 25, 2006, at 11:55 AM, Frank wrote:
Why is the record count so low after conversion to InnoDB?
Who should I believe: InnoDB or MyISAM?
Any ideas as to what can be done to avoid loss of this many rows?
InnoDB doesn't keep a count on number of rows, like MyISAM does.
InnoDB only main
I have a table of type MyISAM that is reporting 47 million rows when I do a
SELECT COUNT(*). When I convert this table to InnoDB, running a SELECT
COUNT(*) returns only 19 million rows. The conversion confirms 19 million
rows were inserted and reports no warnings or duplicates.
I have done the co
I'm trying to switch from myisam to InnoDB. I've edited my.cnf (see below).
When I try to start mysql-max:
[root@db1 mysql]# safe_mysqld --skip-bdb
Starting mysqld-max daemon with databases from /home/dbclnbs/mysql/
011203 15:00:00 mysqld ended
Error log:
011203 14:59:54 mysqld started
InnoD
