Suggested Criteria for Database Table Compression

Hi,

We are about to move some large databases (150Gb to 270Gb) from SQL2005 to SQL2012. One feature that is now available is Database Compression. I do not really see any advantage to compressing a table with less than say 10k rows and does not get many accesses. Does anybody have a good criteria that makes a table a good candidate for compression? We don't have any 10 million row history tables that would be a no-brainer.

Should they be at least x rows and have plenty of reads and liitle updates? Something along those lines.

Thanks

Chris