Archives of the TeradataForum
Message Posted: Wed, 30 May 2001 @ 15:21:33 GMT
| Subj: || || Re: Compress |
| From: || || Adam DeYoung |
Because COMPRESS only is allowed for one specific value in a field as of today, I would suggest reviewing the column definitions to save
space globally. Perhaps you've already examined this but it is worth mentioning.
Use VARCHAR vs. CHAR for longer text columns to save bytes (your definition of 'longer' may vary, but anything over CHAR(5) warrants
examination in our shop). Use SMALLINT or BYTEINT vs INTEGER or FLOAT/REAL where the column values allow it. With no performance pentaly,
the space savings can be significant on tables with big row counts or many long CHAR fields, and you maintain the savings even when the
column value you set COMPRESS on last month is no longer the most frequent value for that column now.