SQL Server Performance

Log shipping and shrink transaction log

Discussion in 'SQL Server Log Shipping' started by feann, Apr 12, 2005.

  1. feann New Member

    Log shipping is configured on the primary server. If there is a task to shrink the transaction log at the mid night, will there be any impact. Thanks
  2. satya Moderator

    Why do you want to shrink the transaction log, when the log shipping is taking care of size.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  3. feann New Member

    since wanna reduce the time to perform full backup of database
  4. satya Moderator

    There is no link to slowdown the full backup if the Transaction log is huge.
    If the log shipping schedule is taking care of transaction log backup then the virtual log truncation occurs at these points:
    - At the completion of any BACKUP LOG statement.
    - Every time a checkpoint is processed, provided the database is using the simple recovery model. This includes both explicit checkpoints resulting from a CHECKPOINT statement and implicit checkpoints generated by the system.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  5. fudiu New Member

    there should be no impact on log shipping if shrinking the log after the full backup?
  6. satya Moderator

    I wouldn't go this path if the disk space is not an issue and no point of doing this as the log shipping is taking care of virtul log sizes. I feel you're stressing SQL resources a bit to reverse the process everytime.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page