Try OpenEdge Now
skip to main content
Trend Database Guide and Reference
Managing OpenEdge Management Trend Database Data : Managing the OpenEdge Management Trend Database size : Sizing guidelines for the OpenEdge Management Trend Database : Example
 
Example
For this example, the following quantities of trends are used for one trend sample:
*5 alerts
*10 tasks (jobs and/or reports)
*25 database files
*10 areas
*10 checkpoints
*25 system disks
*25 file systems
*5 FileSize
*50 Database Analysis
*50 Index Analysis
The following are single rows in the OpenEdge Management Trend Database:
*Samples
*Activity for APW
*Buffers
*Index
*I/O by type
*Locks
*Logging (AI and BI)
*Records
*Servers
*Summary
*Network
*CPU
*Memory
*Status
Note: If Table Statistics and Index Statistics are trended, there are 50 rows of each.
The sample resources will render approximately 12.2K worth of data stored in the OpenEdge Management Trend Database. This data is broken down as follows:
*Database — 3.4K
*System information — 4.1K
*Configuration information (including tasks) — 3.0K
*Index information (for all of the above samples) — 1.7K
If Table Statistics and Index Statistics are trended, they result in 5.4K and 7.1K worth of data, respectively. Additional index information for Table and Index Statistics rows results in approximately 920 bytes.