Hello.
Right, I agree with you for MyISAM tables, however, in my opinion, for InnoDB indexes should be created before populating the table (the link below related to LOAD DATA INFILE statement, but I think, the same applies for INSERT as well): http://lists.mysql.com/mysql/181445 Scott Noyes <[EMAIL PROTECTED]> wrote: > Some sections of the manual seem to indicate that it's better to > create indexes after data population, rather than before. See section > 7.2.14, "Speed of INSERT Statements". The general procedure there is > to load the data using LOAD DATA INFILE, and then use myisamchk. "This > creates the index tree in memory before writing it to disk, which is > much faster because it avoids lots of disk seeks. The resulting index > tree is also perfectly balanced." (ibid) > > On 8/4/05, Michael Stassen <[EMAIL PROTECTED]> wrote: -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
