Readers like you help support MUO. When you make a purchase using links on our site, we may earn an affiliate commission. Read More.

I am creating a .PHP based application which will record accounting entries for specific areas. To handle entries, I am creating a separate table for all areas.

The table name will include the area name as well as the date on which it was created and the table will contain a unique ID, particulars, debit and credit.

So, my question is: Should I create separate table for all areas, will it affect the performance?

James B
2014-06-18 13:12:24
I assume you mean MySQL, since PHP isn't a database. I'm not a database expert by a long shot, but my answer would be: separate data only where it makes logical sense to do so. If the only way in which this data differs would be an "area" column, it would make logical sense to make a single table.
MAKEUSEOF VIDEO OF THE DAY
SCROLL TO CONTINUE WITH CONTENT
Bruce E
2014-06-20 18:11:47
Using a date in a table name is not useful in any way I can conceive. If the table of areas only contains the areas themselves and it's ID, it is useless as well. From the information you have supplied, you should be using one table. Period.