December 2, 2008 at 4:24 am
Hi there,
I have been wondering what advantages I could gain using the new compression techniques in SQL Server 2008. I have tried out turning it on for some of our larger tables and was pleasantly surprised to see that we save enormously with both disk space and i/o performance.
I am now wondering if this compression will have any bearing on a transactional and merge replication we have running. I know that the snapshots can be compressed, but will this have the same effect as the compression of table contents?
Any comments are more than welcome.
Regards,
GermanDBA
Regards,
WilliamD
December 2, 2008 at 12:43 pm
I believe that the replicated data is also compressed, however that you would have to turn on compression on the replicated table manually in order to get the benefits on that side.
December 3, 2008 at 12:45 am
Hi Nicholas,
thanks for the quick reply!
So you mean that the source and target tables would both have to have the compression turned on for this to fully work?
If the source table is marked as compressed and a snapshot is created, the target table should then be created in the same way right? (Obviously as long as the target server supports compression)
Well, we are still only looking at the possibilities, but if we do go this way I will post my results on here.
regards
GermanDBA
Regards,
WilliamD
December 3, 2008 at 5:27 am
Just been flicking through BOL and it appears as though my earlier statement was not accurate, there is a way you can enable it to compress on the subscriber side without having to make manual schema moditifcations.
Take a look at http://msdn.microsoft.com/en-us/library/cc280449.aspx
December 3, 2008 at 5:55 am
Hi Nicholas,
many thanks for the tip. I have not gotten round to reading BOL for SQL 2008, actually the first place I should have looked......
Well the answer is there plain as day.
Thanks again.
GermanDBA
Regards,
WilliamD
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply