Structure Question - One Table or One Table Per Record Set?

Posted on 16th Feb 2014 by admin

I have a web app (mySQL and PHP) which allows people to create an item with up to 200 records which I store in a single table. Any user subscribing to that item will be pulling up to 4 records from the original 100 records each time they load a page. Sometimes the 4 records are chosen randomly and could take many selects to get 4 correct records.

I expect thousands of items to be created, which could lead to millions of records and thousands of millions (I think they call them billions) of selects.

Will this approach scale or should I be creating new tables for each set of records? This could lead to thousands of tables on the DB. Any problems there?

Other forums