Database capacity planning
The data traffic pattern and data volume varies for each installation, because each customer has different monitoring requirements. The following table should be subjected to trend analysis to establish storage needs because they can potentially contain a large volume of data.
Table name | Data stored | Growth potential | Growth limita |
|---|---|---|---|
auditendevent | audit | high | no |
auditstartevent | audit | high | no |
qp_btm_hdlr | compressed history | medium | no |
qp_es_jnl_inputs | journal | high | no |
qp_es_jnl_insts | journal | high | no |
qp_es_jnl_ndflw | journal | high | no |
qp_hdalmjnl | journal | high | no |
qp_hdhr | collected history | high | yes |
qp_hdlr | compressed history | high | yes |
qp_hosts | discovery and registration | medium | no |
qp_nodes | discovery and registration | mediumb | no |
qp_obj_info | discovery and registration | medium | no |
qp_tthr_00 - 07 | collected history | very high | yes |
- See History compression.
- For a very large monitored environment, growth potential can be high.
Comments