1 table many fields/several tables less fields?
Greetings. I would thank some feedback on this issue. The doubt is: Should i create a table, with about 40-65 fields (ID, 3 or 4 of text, the reamining of small/tiny int), or should i split it in about 4-6 tables, dividing the fields between them? Info: The database would be read/write by PHP, and it would have around 1500-2500 users (distributed by the day), with about 150 queries each user. In each query, around 10-20 fields values would be needed. The queries would mainly be SELECT and UPDATE... I did read the optimisation part in the manual, particularly: It's not normally useful to split a table into different tables just because the rows gets 'big'. From http://www.mysql.com/doc/T/i/Tips.html , Other Optimisation Tips. http://www.mysql.com/doc/C/r/Creating_many_tables.html, Drawbacks to Creating Large Numbers of Tables in the Same Database but still didnt got an straight answer for my precise case. Unfortunally i'm new at this (both MySQL and PHP), so i apolozige for any mistake/stupidity presented in the question... :) I will, in lack of contrary info, use 1 table with many fields... Thank you for any comments. Gath - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: 1 table many fields/several tables less fields?
Here are the 5 Rules of Data Normalization -- http://www.datamodel.org/NormalizationRules.html Eliminate Repeating Groups - Make a separate table for each set of related attributes, and give each table a primary key. Eliminate Redundant Data - If an attribute depends on only part of a multi-valued key, remove it to a separate table. Eliminate Columns Not Dependent On Key - If attributes do not contribute to a description of the key, remove them to a separate table. Isolate Independent Multiple Relationships - No table may contain two or more 1:n or n:m relationships that are not directly related. Isolate Semantically Related Multiple Relationships - There may be practical constrains on information that justify separating logically related many-to-many relationships. C:- -Original Message- From: Gath [mailto:[EMAIL PROTECTED]] Sent: Monday, March 25, 2002 1:35 PM To: [EMAIL PROTECTED] Subject: 1 table many fields/several tables less fields? Greetings. I would thank some feedback on this issue. The doubt is: Should i create a table, with about 40-65 fields (ID, 3 or 4 of text, the reamining of small/tiny int), or should i split it in about 4-6 tables, dividing the fields between them? Info: The database would be read/write by PHP, and it would have around 1500-2500 users (distributed by the day), with about 150 queries each user. In each query, around 10-20 fields values would be needed. The queries would mainly be SELECT and UPDATE... I did read the optimisation part in the manual, particularly: It's not normally useful to split a table into different tables just because the rows gets 'big'. From http://www.mysql.com/doc/T/i/Tips.html , Other Optimisation Tips. http://www.mysql.com/doc/C/r/Creating_many_tables.html, Drawbacks to Creating Large Numbers of Tables in the Same Database but still didnt got an straight answer for my precise case. Unfortunally i'm new at this (both MySQL and PHP), so i apolozige for any mistake/stupidity presented in the question... :) I will, in lack of contrary info, use 1 table with many fields... Thank you for any comments. Gath - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: 1 table many fields/several tables less fields?
At 21:34 + 3/25/02, Gath wrote: Greetings. I would thank some feedback on this issue. The doubt is: Should i create a table, with about 40-65 fields (ID, 3 or 4 of text, the reamining of small/tiny int), or should i split it in about 4-6 tables, dividing the fields between them? Info: The database would be read/write by PHP, and it would have around 1500-2500 users (distributed by the day), with about 150 queries each user. In each query, around 10-20 fields values would be needed. The queries would mainly be SELECT and UPDATE... I did read the optimisation part in the manual, particularly: It's not normally useful to split a table into different tables just because the rows gets 'big'. From http://www.mysql.com/doc/T/i/Tips.html , Other Optimisation Tips. http://www.mysql.com/doc/C/r/Creating_many_tables.html, Drawbacks to Creating Large Numbers of Tables in the Same Database but still didnt got an straight answer for my precise case. What was wrong with the information in those sections? That is, what's special about your case that makes them inapplicable? Unfortunally i'm new at this (both MySQL and PHP), so i apolozige for any mistake/stupidity presented in the question... :) I will, in lack of contrary info, use 1 table with many fields... Thank you for any comments. Gath - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
