Does the transaction log on a publisher SQL server get truncated when the database is backed up, but the distributor is down?

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • mokles
    #1

    Does the transaction log on a publisher SQL server get truncated when the database is backed up, but the distributor is down?

    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


    Tags: None
    • Dan Guzman
      #2
      Re: Does the transaction log on a publisher SQL server get truncated when the database is backed up, but the distributor is down?

      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:ncWdnd5XiK zAojvfRVn-sA@rogers.com.. .[color=blue]
      > 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
      >
      >[/color]


        Comment

        • mokles
          #3
          Re: Does the transaction log on a publisher SQL server get truncated when the database is backed up, but the distributor is down?

          Dan Guzman,

          Thanks for your confirmation and explanation.

          Mokles

          "Dan Guzman" <guzmanda@nospa m-online.sbcgloba l.net> wrote in message
          news:ZSspe.1864 $751.1493@newss vr30.news.prodi gy.com...[color=blue]
          > 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[/color]
          by[color=blue]
          > the distributor
          >
          > --
          > Hope this helps.
          >
          > Dan Guzman
          > SQL Server MVP
          >
          > "mokles" <mokles@rogers. com> wrote in message
          > news:ncWdnd5XiK zAojvfRVn-sA@rogers.com.. .[color=green]
          > > Hello All,
          > > The setting is SQL server 7, on Windows NT.
          > >
          > > If the distributor can not access the log on the publisher database ([/color][/color]
          but[color=blue][color=green]
          > > 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[/color][/color]


            Comment

            Previous template Next
            Working...