Algorithmic compression in DBQL History tables

Database
Enthusiast

Algorithmic compression in DBQL History tables

I am considering the impementation of algorithmic compression within our 13.10 system's DBQL History tables. We have quite a long retention requirement for this data and the daily maintenance and nightly backups are starting to become an issue because of the large sizes. I have used the Atanasoft CompressTool to identify canidates for muti-value compression and recently implemented the recommendations. This has helped significantly, especially for the DBQLogTbl, but long strings such as the query text, queryband and logon strings are untouched. I thought these particular columns would possibly benefit from AC. I have read the documentation on compression but am still concerned about performance during the nightly historical processes and retrieval.

Has anyone else condidered or implemented algorithmic compression within these historical tables. Any other suggestions that may be beneficial.

Does anyone else have extended retation requirements for their historical DBQL data and approaches the problem from a different angle?

2 REPLIES
Enthusiast

Re: Algorithmic compression in DBQL History tables

ALC seems to work just fine. It didn't do a whole lot on the DBQLog table but I saw a significant compression rate of 80% with LZCOMP.

NTA3239 just surfaced. It concerns possible corruption when using mvc/alc and loading a table with fastload or multiload.

Tables in the DBQL history are loaded with a bteq so I am safe there. 

Enthusiast

Re: Algorithmic compression in DBQL History tables

Just reread my post.  

I meant to say that I got an 80% compression with LZCOMPon the DBQLSQL table.