Post reply

Subscriber DB size is growing larger than Publisher

  • August 21, 2012 at 11:13 am

    #260887

    hi all,

    i have an issue Subscriber DB size is growing larger than Publisher , publisher db is 21gb , but subscriber db is 72 gb i am using transactional replication .

    can any one suggest me why subscriber is growing .

    Thanks,

    Ashwin

  • August 21, 2012 at 11:38 am

    #1528282

    ashwinboinala (8/21/2012)

    hi all,

    i have an issue Subscriber DB size is growing larger than Publisher , publisher db is 21gb , but subscriber db is 72 gb i am using transactional replication .

    can any one suggest me why subscriber is growing .

    Thanks,

    Ashwin

    First, imho, this would be a better post for High Availability.

    Have you compared the transaction log growth between the publisher and subscriber db? Whats the recovery model on both databases?

    "I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

    -- Itzik Ben-Gan 2001

  • August 21, 2012 at 11:44 am

    #1528288

    its recovery model is full and the problem is there are duplicate entries in db

  • August 21, 2012 at 1:39 pm

    #1528352

    ashwinboinala (8/21/2012)

    its recovery model is full and the problem is there are duplicate entries in db

    Well there's your problem 🙂

    Jared
    CE - Microsoft

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

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