----- Original Message ----- > From: "Hank" <[email protected]> > > I'm trying to rebuild an index after disabling all keys using > myisamchk and adding all 144 million records, so there is no current index on > the > table.
Ahhh... I didn't realise that. > But in order to create the index, mysql has to do a full table scan > AND a sort, which for 144 million records, is going to take a very long > time. So an un-indexed full table scan without an index (i.e ..."HAVING > count(*)>1") will actually take less time. > > So like I said, it would be intuitive and helpful if the tool finding > the dup records actually provided enough info to view, find, and fix them > so I don't have to index, sort, or table scan the table a second time. Hah, yes. I have to say I'm not aware of anything that does that, maybe one of the Percona guys knows something. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[email protected]
