note: freqency of data, size (kb), size (number of fields), size (number of tables)

The number of records a system holds is an important factor in right-sizing system spend.

I've seen millions of dollars spent on systems that don't hold millions of records. The cost per record seems high, relatively to other solutions.

It is possible to quantify the frequency of data creation and updating, as well as the volume of data flowing through a system, in terms of records and bytesize.

Written more? (recording stock transactions) Is data read more? (viewing stock transactions from a cache)