It does speed things up to have no indices, sure. How much, I do not know exactly. It takes CPU time to update the index, time to write it to disk, etc.
I have always used indices heavily, since I have tended to work with data that needs to be sliced & diced lots of different ways. I personally consider it to be good database design to always have a primary key unique id number in my tables - but in some cases it's just plain not needed. Yours may be just such a case, since it's just logging data. Do you feel you need such a unique identifier? If you feel you do, add it. If you notice it's slowing things way down and that is unacceptable, you could evaluate whether to start tweaking performance / upgrading hardware, or just removing the column from the table. HTH, Dan On 10/21/06, Brett Harvey <[EMAIL PROTECTED]> wrote:
Does not having a Primary Key and No indexes really speed up inserts significantly? We have a log table. it has the fields, cart_id, referer, remote_ip, server_name, user_agent, company, action, type, and value that we are tracking vistor log information for our ecommerce site. Every page is tracked that a person goes to in the log file. Currently we have about 500,000 rows. So I am wondering if we are really saving that much by not having a Primary Key and no indexes. Thanks! -- -------------------------------------------------------------------------------- /Brett C. Harvey; /Creative-Pages.Net, President; /Facility Management Systems, CTO (www.fmsystems.biz); /Lasso Partner Association Member ID #LPA135259 (www.omnipilot.com/www.lassopartner.com); -------------------------------------------------------------------------------- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
