Gleb: Aha. OK, we tried using OPTIMIZE instead of ANALYZE, and that does indeed update the Cardinality of the index, the way you would expect. Thanks very much for figuring this out! I really appreciate the help.
Thanks again! Allan "Gleb Paharenko" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hello. > > I've checked this and found that ANALYZE table really doesn't work, but > OPTIMIZE table made its work. In case it won't help you send to list > complete definitions of you tables and queries. > > > Allan Miller wrote: > > Hi Gleb, > > > > Thanks for the quick response. Unfortunately, ANALYZE TABLE does not > > appear to affect the Cardinality field of a temporary table (it is > > still NULL, even with rows added). Only by creating the index itself > > after the insert seems to make the query faster. I also tried FORCE > > INDEX and it did not make things any faster. > > > > Do you have any idea why creating the index AFTER putting the data in > > the table affects the performance so dramatically? > > > > Allan > > > > > -- > 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]
