Advertisement
Since archive data contain no indexes, they occupy less
• Expire - pertains to the action of dropping data from the
Expiration Rules
The administrator of the Server specifies the number of
weeks of data that will be stored on the Server, based on the
storage capacity of the hard drive, and the number of hits on
the Server. After inputting the percentage of live data to be
stored, the Server translates that figure into the equivalent of
weekly time periods for live and/or archive data storage.
When the Server reaches the maximum number of weeks
allocated for live data storage, the oldest week of live data
stored on the Server attains an archive data status. In attain-
ing an archive data status, the index for that week of data is
dropped from the database tables.
When the Server reaches its maximum number of weeks
allocated for archive data storage, the oldest week of non-
indexed data stored on the Server is automatically dropped
(expired) from the database.
Once data expires, it cannot be recovered.
8
6 T
, E
E
ECHNOLOGIES
NTERPRISE
A
DMINISTRATOR
space on the Server than live data—which include indexes
and pages/objects. However, reports generated for periods
of time with archive data take longer to process since
indexes are not included for that data.
Server when there is no room left on the hard drive for
additional storage. When the hard drive reaches its maxi-
mum data storage capacity, indexes from the oldest week
of data stored on the Server are dropped, or "expired" from
the Server. Thereafter, when more space is needed on the
Server, the oldest week of non-indexed data "expires."
R
3.0 U
'
EPORTER
SER
S
: C
ECTION
HAPTER
G
S
UIDE
2 - C
ER 3.0 S
ONFIGURING THE
ERVER
69
Advertisement
