Database efficiency – table per user vs. table of users

The database layout should not change when you add more data to it, so the user data should definitely be in one table.


  • Having multiple tables means that you have to create queries dynamically.

  • The cached query plan for one table won’t be used for any other of the tables.

  • Having a lot of data in one table doesn’t affect performance much, but having a lot of tables does.

  • If you want to add an index to the table to make queries faster, it’s a lot easier to do on a single table.

Leave a Comment