OpenEdge Getting Started: Multi-tenancy Overview - Product ...
OpenEdge Getting Started: Multi-tenancy Overview - Product ...
OpenEdge Getting Started: Multi-tenancy Overview - Product ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 1: Introducing multi-<strong>tenancy</strong><br />
Figure 1 depicts the allocation of data objects across storage areas in a multi-tenant<br />
database with two defined tenants, ABC Corp and BUS Corp.<br />
Default<br />
Migrated data<br />
Deallocated data<br />
Shared<br />
Data Physical Storage<br />
Tenant : ABC Corp<br />
Tenant : BUS Corp<br />
A7<br />
ABC<br />
data<br />
A11<br />
BUS<br />
data<br />
A15<br />
Default<br />
data<br />
A9<br />
ABC<br />
Indexes<br />
A14<br />
BUS<br />
Indexes<br />
A16<br />
Default<br />
Indexes<br />
A17<br />
Shared data<br />
Figure 1: Physical storage in an multi-tenant database<br />
A8<br />
ABC<br />
LOBs<br />
A12<br />
BUS<br />
LOBs<br />
A19<br />
Default<br />
LOBs<br />
A18<br />
Shared<br />
Indexes/<br />
Shared LOBs<br />
The left-hand side of Figure 1 shows the logical representation of the database, and<br />
shows two regular tenants and the default tenant. The Shared section represents data<br />
that all tenants can access. The Shared section contains all non-multi-tenant data as<br />
well as the database schema area.<br />
The right-hand side of Figure 1 shows a representation of the physical storage of the<br />
database. In this example, each tenant has a distinct area for each default area.<br />
Note: <strong>Multi</strong>-tenant partitions must be stored in Type II areas. Shared data can be<br />
stored in either Type I or Type II areas. The schema area is always a Type I<br />
area.<br />
36 <strong>OpenEdge</strong> <strong>Getting</strong> <strong>Started</strong>: <strong>Multi</strong>-<strong>tenancy</strong> <strong>Overview</strong>