> I will build a web application and use H2 as the database system (server > mode). > > The system will have 3 main tables, they will not be large in number of > columns, but they will have millions of rows some day. > > Each customer will have totally separate data inside each table, > identified by customer ID. > > Considering performance, my question is: what is the best approach for H2? > > a- 1 database with single tables (3 tables in this case, with a > column/index customerID in each table) > > b- 1 database with multiple tables (3 separate tables for each customer) > > c- 1 database per customer > What about only one database, but a schema per customer ?
This allows very easily to later move one or some of the customers to other databases or machines. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
