winmansoft, you should also be aware of the 14-byte-per-row overhead that READ_COMMITTED_SNAPSHOT requires. Anytime a row is updated, or a new row is inserted, the 14 bytes will be added. This can cause page splits if you don't have enough freespace in the page to hold the extra 14 bytes for each row updated.
There is also a big initial performance hit for any "old-style" ntext, text, and image columns (but not for the newer (max) data types). After RCS is enabled, the first time one of those "old-style" large columns are updated, SQL will have to rewrite the entire value, possibly using more pages (since each page holds 40 less bytes).
SQL DBA,SQL Server MVP(07, 08, 09)[size=2]Prosecutor James Blackburn, in closing argument in the Fatal Vision murders trial: If in the future, you should cry a tear, cry one for them [the murder victims]. If in the future, you should say a prayer, say one for them. And if in the future, you should light a candle, light one for them.[/size]