Once compressed, I think you might also want to create an export/backup of the table, then drop the table, then re-create the table with SQL as empty, and then load the table with data from the export/backup. I've found in the past, at least with Oracle, that if the tables row count grows too big then it takes up too much space on disk and once the record count goes from something like 1 million to 1 thousand the performance is still horrible when accessing the table. Re-creating and re-loading the table will re-create the table as a much smaller size making it possibly more efficient to query on disk. I do this with tables that tend to get exercised a lot (from lots of rows to few rows, over and over again).
