Owner's Manual

897

Database Sizing

Introducing Database Sizing

This appendix suggests sizing solutions, but any final sizing decisions must realistically be guided

by business managers working with DBAs to weigh data storage requirements versus costs.

NOTE:

A typical recommendation is to size your database 20% larger than the expected data.

You can store roughly 0.5 million traps per 1G of disk space. Performance typically does not suffer if

you oversize. Twenty gigabytes of storage is typical.

Database Aging Policy

This application includes a Database Aging Policy (DAP) Manager, which lets you set up policies

that control the length of time that data persists in the database. Best practice is to set up DAPs for

records that are continually persisted. Several aging policies come with the application. You can

edit them to suit your needs, too. Consult the

User Guide

for information about how to do this.

See Chapter 7, Database Management for more information about database backup.

Autoextend

The embedded MySQL database lets you define an initial size and an autoextend ceiling. This

ceiling is a hard coded value in the MySQL config file. To change this, define the following in the

my.ini/my.cnf

files at creation time:

[Installation root]/oware3rd/mysql/ibdata/

ibdata1:1024M:autoextend:max:2048M

What this says is to create a 1G data file at initiation and allow it to grow to a maximum of 2G, as

needed. Once 2G is reached the server will start issuing errors (number 1114) for each insert

attempted. If this occurs, you must add another data file to the system and revise Database Aging

Policies accordingly.

The installer also lets you choose these MySQL values, defaulting to 1024M for initial and 8096M

for the ceiling.

One example system would add a data file to the database to account for alarm/event history data: