Full back ups and transaction logs

Running 2005 with sp2. It seems that when running a full back up set as a
maintenace plan the transaction logs are filling up and do not shrink back.
The database is set to FULL recovery. Can some please assist me thank youFull backup does not empty the log. Use BACKUP LOG for that. If you don't want to do log backups,
set the recovery model to simple.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Victoria Morrison" <VictoriaMorrison@.discussions.microsoft.com> wrote in message
news:844C7B8A-2E4D-46F0-A51B-CAD917959C64@.microsoft.com...
> Running 2005 with sp2. It seems that when running a full back up set as a
> maintenace plan the transaction logs are filling up and do not shrink back.
> The database is set to FULL recovery. Can some please assist me thank you|||A FULL backup does nothing to clear the transaction log in FULL recovery
mode. You need regular LOG backups for that to happen. Even a LOG backup
will not shrink the file, it only allows committed and backed up portions of
the log to be reused. If you are in FULL recovery mode and wish to reap the
benefits of that you must do regular LOG backups, otherwise change the
recovery mode to Simple.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Victoria Morrison" <VictoriaMorrison@.discussions.microsoft.com> wrote in
message news:844C7B8A-2E4D-46F0-A51B-CAD917959C64@.microsoft.com...
> Running 2005 with sp2. It seems that when running a full back up set as a
> maintenace plan the transaction logs are filling up and do not shrink
> back.
> The database is set to FULL recovery. Can some please assist me thank
> you|||My questions is why would the back up cause the transaction log to grow and
grow. I do not recall this happending in 2000.
"Tibor Karaszi" wrote:
> Full backup does not empty the log. Use BACKUP LOG for that. If you don't want to do log backups,
> set the recovery model to simple.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Victoria Morrison" <VictoriaMorrison@.discussions.microsoft.com> wrote in message
> news:844C7B8A-2E4D-46F0-A51B-CAD917959C64@.microsoft.com...
> > Running 2005 with sp2. It seems that when running a full back up set as a
> > maintenace plan the transaction logs are filling up and do not shrink back.
> > The database is set to FULL recovery. Can some please assist me thank you
>|||The backup has nothing to do with the logs growing. It is the transactions
you are issuing that cause the log to grow and if you don't issue regular
Log backups this will keep happening. Something you may be encountering is
that even if you are in FULL recovery mode, until you issue a valid FULL
backup it will act as if it was in Simple mode and truncate the log when 70%
full. As soon as you issue a FULL backup it will expect you to also issue
regular Log backups. So I suspect no one ever did a FULL backup on the old
db.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Victoria Morrison" <VictoriaMorrison@.discussions.microsoft.com> wrote in
message news:4B79C133-8BFC-4841-B36D-FDD6482811E1@.microsoft.com...
> My questions is why would the back up cause the transaction log to grow
> and
> grow. I do not recall this happending in 2000.
> "Tibor Karaszi" wrote:
>> Full backup does not empty the log. Use BACKUP LOG for that. If you don't
>> want to do log backups,
>> set the recovery model to simple.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Victoria Morrison" <VictoriaMorrison@.discussions.microsoft.com> wrote in
>> message
>> news:844C7B8A-2E4D-46F0-A51B-CAD917959C64@.microsoft.com...
>> > Running 2005 with sp2. It seems that when running a full back up set
>> > as a
>> > maintenace plan the transaction logs are filling up and do not shrink
>> > back.
>> > The database is set to FULL recovery. Can some please assist me thank
>> > you