Hi Wolfgang, I'd say it somewhat depends on what data you have and what you really are going to use the records for. If you never need to retrieve data for more than one product at a time and there are significant differences in the data set between the products then maybe you might split it. Otherways you will complicate things a lot by not having them in the same table. And is the data set (not) the same for all the products ? And will you get more products in the future (ending up adding tables) ? I would anyway go for the one table solution if there isn't any significant reason to split it on 26 separate tables. And then of cause the data normalisation issue is another thing.
Jan -----Original Message----- From: W. Bauer [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2003 21:41 To: [EMAIL PROTECTED] Subject: Several tables or huge single table? Dear all I have a table with more than 100'000 records for a single product. At the end, I will have tables for 26 prodcuts. There is basically no dependence on other tables. Somewhere I read that one should avoid a large number of tables in a database. Is it more recommendable to have a single huge table for all products togehter or is it better to keep 26 distinct tables? Thanks for a hint, Wolfgang Bauer -- 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]
