MySQL Forums
Forum List  »  Optimizer & Parser

Re: big database +1 million rows/days
Posted by: Rick James
Date: September 13, 2013 10:59PM

In order to answer your question, we need to know what you will be doing with the data. Do you have the SELECTs that will be fetching it?

Normalization will shrink the 'fact' table. Shrinking it will save space, hence I/O, hence speed. Normalization may require some code; are you using Perl/Java/etc?

int(30) does not make sense. How big will the numbers really be? Probably INT UNSIGNED will work for you; it has a max of 4 billion.

What column or combination of columns is unique?

KEY `value` (`value`),
KEY `value_2` (`value`)
Those are redundant; DROP one of them.

> 1 million rows/days
Which table are you referring to?

> Object: parameter1 = value1 , value2, value3,....;
Too vague; please show use the SQL and/or sample of the data.

Don't use FOREIGN KEYS, that slows things down.

Options: ReplyQuote


Subject
Views
Written By
Posted
2883
September 11, 2013 04:06AM
Re: big database +1 million rows/days
1173
September 13, 2013 10:59PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.