What we are interested in is how database performance in a multi-tenancy environment.
What is a multi-tenancy environment? Can you give some background pointers?
What I am now focus on is how new schema and tables are created and kept on the hard disk and how Derby load them into memory when the database boots up.
Each table is a separate operating system file, called a "conglomerate" in the Derby internals. Indexes are also separate conglomerates. Information about the schema is kept in a master set of system catalogs, which are documented in the derby docs. Tables and indexes are created with CREATE TABLE and CREATE INDEX statements. Tables are not loaded into memory when the database boots, but rather are opened on demand when referenced by a user's SQL (excepting the special case of database recovery, which does access the tables at boot). thanks, bryan
