*I am asking this on SO not SF because I am a developer and am interested in the data access performance aspects of this not the Administration aspect.
I've been trying to do some research / learning into the underpinnings of TABLE | INDEX ... ROW | PAGE Compression. There is a wealth of information about how to implement these features and I am aware of the basic concepts that while you are using slightly more CPU it is negligible v I/O saved. However I am failing to find a very detailed explanation of when this should be utilized when it is not appropriate to utilize and when to use page v row. Even in several books I have read on performance tuning a database architecture ( they seem to just go on about how great it is and then gloss over the internal underpinnings).
Even this SQLCAT article on MSDN (while the most in depth I have found) doesn't really seem to do the topic justice. I have some rough ideas, as in a heavy OLTP application with allot of updates and inserts the CPU penalty may weigh more heavily against the gains in I/Os.
If anyone can provide me with a good explanation or point me in the direction of some detailed literature I would greatly appreciate it.
Thanks in Advance