I have a table in my database (currently) that grows to be huge (and I
need to keep the data). I'm in a redesign phase and I'm trying to do it
right. So here are the relevant details:
The table has several keys involved:
mysql> desc data__ProcessedDataFrames;
+------------------------+------------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra
|
+------------------------+------------------+------+-----+---------+----------------+
| processed_id | int(10) unsigned | NO | PRI | NULL |
auto_increment |
| top_level_product_name | varchar(255) | YES | MUL | NULL |
|
| test_id | int(10) unsigned | YES | MUL | NULL |
|
| p_time | double | YES | MUL | NULL |
|
| processed_data | mediumblob | YES | | NULL |
|
+------------------------+------------------+------+-----+---------+----------------+
6 rows in set (0.00 sec)
This is the table that contains the data I'm interested in currently.
Queries on this table when it gets large is slow as molasses. I'm
thinking about making a new table for anything with a different test_id
.... any opinions as to whether this is good or bad?
Before you make fun of me for my questions, I a bit new to database
programming.
If it is better design to break it into smaller tables (for speed anyway)
then I would need to know how to query over multiple tables as though it
was one table. Join will do this, but that takes forever (unless of
course I may be doing this wrong), so that's not a good option. I need to
be able to query over mutiple test_ids, which will be multiple tables, for
specific top_level_product_name, with in some time range (using p_time).
Any help would be appreciated. I will happily give more information if
you need to offer an educated opinion.
Thanks
David Godsey
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
