 |
 |
Archives of the TeradataForum
Message Posted: Fri, 28 Jan 2011 @ 20:52:05 GMT
Subj: | | Re: Compressing infrequent values |
|
From: | | Gregg, William |
Another consideration is the stability of the values. If the domain of the attributes is stable, then compressing the low frequency values may
contribute to space savings.
When volatility is high (enuff) then compressing the values that account for small space savings is usually not worth the effort. These values
often roll off the plus side of the ledger to the negative side. Avoid trying to split hairs when compressing data. Follow the 80-20 rule.
If U compress your top 64, U get most of the savings -- sometimes the top 128.
Rgrds,
Bill Gregg
Teradata DBA
| |