Posted by mokles on 06/09/05 06:55

Dan Guzman,

Thanks for your confirmation and explanation.

Mokles

"Dan Guzman" <guzmanda@nospam-online.sbcglobal.net> wrote in message
news:ZSspe.1864$751.1493@newssvr30.news.prodigy.com...
> 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: Date/Time Stamp
• Prev in forum: Re: what type of Constraint to prevent duplicates
• 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]