Hi,
Generally, Multi-tenancy means "many customers reside on one
database".
They can share the same database instance or even share the same table.
Here are some links to this topic:
Multi-tenant database design:
http://discuss.joelonsoftware.com/default.asp?design.4.319460.16
Multi-Tenant Data Architecture:
http://msdn2.microsoft.com/en-us/library/aa479086.aspx
Thanks
Yifan
-----邮件原件-----
发件人: Bryan Pendleton [mailto:[EMAIL PROTECTED]
发送时间: 2007年1月29日 16:30
收件人: [email protected]
主题: Re: Derby for multi-tenancy environment
> 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
