jaymc Posted January 10, 2008 Share Posted January 10, 2008 What would you call a cluttered table that could effect performance 100,000 rows of data accumulating 20MB in total, the table structure has 30 fields but the field content is 1 or 0 Or 100,000 rows of data accumulating 50MB in total, the table structure has 10 fields but the field content usernames Im just wondering whether it will cause a problem having a ton of fields in a table, or would it be better to split it into 3 tables and just join.. Join has its overhead, but so does having 30 fields as apposed to 10 Or perhabs fields in a row do not cause any problems at all, rather, the number of rows are what to be carefull with aswell as the content (numbers vrs words) Any advice on this Quote Link to comment Share on other sites More sharing options...
fenway Posted January 10, 2008 Share Posted January 10, 2008 Obviously, they can't be normalized the same way... size of a record is really in issue here, determines number held in various buffers, which determines how fast mysql can perform many operations -- which is why it's bad to have BLOB/TEXT fields mixed in with other data types in general. Quote Link to comment Share on other sites More sharing options...
jaymc Posted January 10, 2008 Author Share Posted January 10, 2008 Perfect! Just what I was after Thanks Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.