MySQL Forums
Forum List  »  Data Warehouse

Re: big data question
Posted by: Rick James
Date: March 31, 2013 01:25AM

The rows are far more than 7 bytes!
So, the table may fill up too soon!

DESCRIBE TABLE does not provide all the information that SHOW CREATE TABLE does.

> In fact we use this to left-join two tables and report incomming call data to the user.
May we see them, plus the EXPLAIN.

> A select query which contains a join and group-by by date would be take a lot of time and the user is not happy.
Summary tables.

> Would it be a help by partitioning both tables base on time

> contains normalized joint data product of both tables
I think you are misusing the term "normalized".

> date1 integer not null,
> time1 integer not null,
Probably better to use a single DATETIME field.

> protocol integer,
How many different protocols do you have? INTEGER can hold numbers up to 2 billion. TINYINT UNSIGNED holes 0..255 and takes only 1 byte (instead of 4).
Similarly, consider shrinking other fields.

Options: ReplyQuote

Written By
March 27, 2013 01:26AM
March 28, 2013 07:52PM
March 30, 2013 06:11AM
Re: big data question
March 31, 2013 01:25AM

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.