Professional Documents
Culture Documents
Changes_16GB_Limit
Changes_16GB_Limit
Changes_16GB_Limit
Enhancements
Objectives
Overview
Notable Changes
Configuring the Configurable Database Size limit
Notable Changes
Size check done against database using logical database size. Empty
space does not count against the configurable limit.
Limit checks done at regular 24 hour intervals by default; controlled by
Store.exe inside of JET.
New key logging events
Log Informational Event at Default logging level for every
database mount operation showing the physical database size as
well as the configured Database Size Limit (Event IDs
1216/1217).
Log a Warning event when the database size is within the
Warning Buffer of the Database Size Limit (Event ID 9688).
Additional event logs for database size check upon mounting,
start of size check task and operations being performed (Event
IDs 9685, 9686, 9687, 9689, 9690). *To be covered later.
Licensed Database Size Limit
* Since the default value of the warning threshold buffer is 10%, that means
with a default DB size limit of 18 GB that the customer will begin to get the size
warnings right around 16GB. (i.e., 10% of 18 GB is ~2 GB. 18 GB – 2 GB
means the warnings occur ~16 GB).
Configuring the Configurable Database Size Limit
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\MSExchangeIS\<SERVER NAME>\Private-<GUID
of the database>
Data Type: REG_DWORD
Name: Database Size Limit in GB
Value:
• Standard: 1 - 75
• Enterprise: 1 - 8000
Check the free space in the database
Configuring the Configurable Database Size
Limit
Database Size Buffer Warning
Overview
How It All Works
Behavior when the Configured Database Size Limit is
reached
Behavior when the Licensed Database Size Limit is
Reached
Configuring the Database Size Event Log Buffer
Database Size Buffer Warning
Pre-SP2, limit checks on the Licensed Database Limit occurred when the
database file size needed to grow (that is, when there was no more free
space to utilize). If it went beyond the licensed limit, the database would
be taken offline.
SP2 and beyond, the server will do the following when the Configured
Database Limit is reached
On first check after mounting, if the database size is above the limit,
the database will not be taken offline and we log error Event ID 9689
On second check, an error event 9690 and dismount the store
When the Licensed Database Limit is reached, the behavior above is
the same
Configuring the Database Size Buffer Warning
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\MSExchangeIS\<SERVER NAME>\Private-<GUID
of the database>
Data Type: REG_DWORD
Name: Database Size Buffer in Percentage
Value: 1-100
Database Size Buffer Warning
Timing of the Database Size Check
By default, timing of the database size check will occur at 5A.M. and run
off 24-hr intervals
Both time and interval are configured via registry per database
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
MSExchangeIS\<SERVER NAME>\Private-<GUID of the database>
• Data Type: REG_DWORD
– Name: Database Size Check Start Time in Hours From Midnight
– Value: 1 – 24
• Data Type: REG_DWORD
– Name: Database Size Check Interval in Minutes
– Value: 1 – 1440
** MS INTERNAL ONLY
Timing of the Database Size Check
Thank You