High subscriber log size

  • Hi.
    I have push snapshot replication and two subscrbers. One subscriber is on SQL 2014 SP2 Enterprise, second on SQL 2016 SP1 Standard.
    I noticed that log file size for SQL 2014 growths to 36GB but for SQL 2016 growths to 53GB. It's a big difference. Any ideas?

  • recovery model?
    Backups?
    Full or Empty log file?
    Index or stats updates/rebuilds different than the other sub?

    Select db_name(database_id),log_reuse_wait_desc
    from master.sys.databases

    ------------------------------------------------------------------------------------------------Standing in the gap between Consultant and ContractorKevin3NFDallasDBAs.com/BlogWhy is my SQL Log File HUGE?!?![/url]The future of the DBA role...[/url]SQL Security Model in Plain English[/url]

  • Publisher and both subscribers has simple recovery model - before each snapshot logs are empty.
    Compability level is the same - 120.
    If i shrink log to the same size (for example 1GB) after synchronization logs reach above size

  • Any post-snapshot activities such as index maintenance happening on the Sub?

    ------------------------------------------------------------------------------------------------Standing in the gap between Consultant and ContractorKevin3NFDallasDBAs.com/BlogWhy is my SQL Log File HUGE?!?![/url]The future of the DBA role...[/url]SQL Security Model in Plain English[/url]

  • Any additional activities.
    Autogrowth settings are the same, also I created similar initial structure for log file (size and number of VLF)

  • Sorry, I'm at a loss...have not done any replication with 2016 yet 🙁

    ------------------------------------------------------------------------------------------------Standing in the gap between Consultant and ContractorKevin3NFDallasDBAs.com/BlogWhy is my SQL Log File HUGE?!?![/url]The future of the DBA role...[/url]SQL Security Model in Plain English[/url]

  • Maybe difference between standard and enterprise...

Viewing 7 posts - 1 through 6 (of 6 total)

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