Justin French <[EMAIL PROTECTED]> wrote: > Should I worry at 40,000? 100,000? Or will the indexing of the siteID > keep everything extensible?
Indexing is designed to keep SELECT speed small with no matter how much data it is. You should ensure that the siteID index is properly used (use EXPLAIN SELECT). Say, if half of the records belongs to a particular siteID - the index won't help, the full table scan will be done to find out the needed article. You may consider creating a complex index as well - say, (siteID, articleID). Then to fetch the list of all articles of a site the (siteID) index will be used, and to fetch particular article the compound index will be used. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [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]
