Limiting precision will help, but will the more limited precision still
deliver the information you want? Did the 2 TB allow for "wasted" space
on the database pages?

DASD is cheaper than programming now. You're talking about < $2,000 of
commodity storage (and some fixed proportion more for RAID). That needs
to be weighed against programmer time.

Also, you may want to separate active data collection (today's data)
from archival material (the last three months) into two physical
databases, with a nightly migration job that spans the two databases.

On Tue, 2005-09-13 at 13:06 +0200, Francesco Lamonica wrote:
> Hi, i am planning a database to hold network traffic measurement data
> (notably bandwidth and number of packets)
> since i will have to store at least three months worth of data the sheer
> extimate in terms of bytes is around 2TB.
> I am wondering if limiting the precision of numerical data fields will help
> keep the db size at reasonable levels. e.g. using 16bit fileds vs 32bit
> ones.
>
> thanks
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>