SQL replication sizes are different between source and destination

  • Hi, have a question. We have snapshot replication set up going from production to lower level servers. The sizes of the databases are very different from production to lower environments. Can you help explain? How can i figure out where differences are:

    Production: 76GB

    Lower Level 1: 22GB

    Lower Level 2: 16GB

    Data appears to be same but as you see the sizes are drastically different. please help explain.

  • I'm not sure if this is the same with snapshot replication as with regular transactional replication but...

    With transactional replication you can choose whether to replicate indexes or not. It may be worth checking your publication settings to see whether you're replicating indexes.

    The other thing is it could come down to fragmentation of indexes. if your source is heavily fragmented then it may be consuming more space than is necessary.

    Thanks,

    Simon



    MCSE: Data Platform
    MCSE: Business Intelligence
    Follow me on Twitter: @WazzTheBadger
    LinkedIn Profile: Simon Osborne

  • In addtion to the above which is the most likely scenario. Are you using any filters in your indexes and are you copying all attributes as part of your articles?

    MCITP SQL 2005, MCSA SQL 2012

  • RTaylor2208 (8/16/2013)


    In addtion to the above which is the most likely scenario. Are you using any filters in your indexes and are you copying all attributes as part of your articles?

    Great catch. I hadn't thought of that.



    MCSE: Data Platform
    MCSE: Business Intelligence
    Follow me on Twitter: @WazzTheBadger
    LinkedIn Profile: Simon Osborne

  • all data is replicated: tables, views, etc...

    thanks for all your help

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply