SQL Server Performance

Error 4305 from Spanish Forum

Discussion in 'SQL Server Log Shipping' started by Luis Martin, Mar 21, 2006.

  1. Luis Martin Moderator

    I was reading error 4305 in this forum, but I think the situation from original post (spanish) is different.

    The problem is:

    Recovery model: Full.
    Transaction log backup: each hour.
    Log Shipping without problem.

    When she (Nuria) run reindex and after that she truncate the log, she has 4305 error.

    Because lack of space she has to truncate that log, and so there is a gap. That gap cause 4305 (this is my conclusion).

    What do you think about the best way to fix the problem? (I have no experience with log shipping).

    Luis Martin

    Although nature commences with reason and ends in experience it is necessary for us to do the opposite, that is to commence with experience and from this to proceed to investigate the reason.
    Leonardo Da Vinci

    Nunca esperes el reconocimiento de tus hijos, eso ocurrirá luego de tu muerte

    All postings are provided “AS IS” with no warranties for accuracy.

  2. simondm New Member

    If shes having to truncate the log then log shipping will break.

    She could use DEFRAG instead on REINDEX and stop before the log fills. Or just backup the log more often, when a REINDEX is done it's not in one transcation - so the log can be backed up during a reindex (I think).

    The only way to continue log shipping after a break in logs is to re-initalise with a full backup/restore. It is possible to resync it with a Diff backup - but this can get tricky.

    Hope this helps.

Share This Page