Posted by Dan Guzman on 06/08/05 05:38

Full backups don't truncate the log; the log is truncated by BACKUP log.
From the Books Online:

<Excerpt href="\tsqlref.chm::/ts_ba-bz_35ww.htm">
Once the log is backed up, the space may be truncated when no longer
required by replication or active transactions.
</Excerpt>

I believe the data is considered required for replication until retrieved by
the distributor

--
Hope this helps.

Dan Guzman
SQL Server MVP

"mokles" <mokles@rogers.com> wrote in message
news:ncWdnd5XiKzAojvfRVn-sA@rogers.com...
> Hello All,
> The setting is SQL server 7, on Windows NT.
>
> If the distributor can not access the log on the publisher database ( but
> subscribers are not deleted yet), will the full backup of the publisher
> database truncate the transaction log? My guess is, it will not truncate
> the
> log.
> Can any one confirm please?
>
> Thanks,
> Mokles
>
>

• Next in forum: Re: SELECT works but UPDATE fails. ?
• Prev in forum: Re: SELECT works but UPDATE fails. ?
• Thread view: Re: Does the transaction log on a publisher SQL server get truncated when the database is backed up, but the distributor is down?

[Reply to this message]