Hello.
In my opinion, something changes in how MySQL handles the query when you overrun the 100,000 number of rows. If EXPLAIN shows the difference for queries with LIMIT below and higher than 100,000? Do you have key_buffer (innodb_buffer_pool_size) big enough? Please send you queries to the list as well. >thanks.. now it uses index by default.. it uses now >idx_delete_phoneoffice_assigneduserid.. and it is fast for LIMITS up to >100,000 but.. after 100,000 it takes more than a second.. at LIMIT >700000,20 it takes 9 seconds... ehhh Marko Knezevic 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]
