transaction log

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: dimitris (dantoniades_at_mshf.com.au)
Date: 03/31/04 

Date: Wed, 31 Mar 2004 12:06:14 +1000

Hi,
I have a database size of 2,5 Gb, and I set the transaction log unrestricted
growth. I backup the database every nite, and next morning the transaction
log goes up to 4 Gb!. If I restrict the log file (to 800Mb) it will get full
within a couple of hours.
If I manually backup the log file and the database and then manually shrink
it 4-5 times, the transaction log goes back to 130 Mb.
Any suggestions?
Jim

Relevant Pages

  • Re: Large Transaction Log Backup after Database Backup
    ... script and see for yourself that the database backup doesn't truncate the ... ALTER DATABASE steve SET RECOVERY FULL ... But my understanding was that the transaction log was> truncated after a full database backup. ...
    (microsoft.public.sqlserver.server)
  • Re: Transaction Log Size
    ... Backup database does not empty the transaction log files. ... How to Shrink the SQL Server 7.0 Transaction Log ...
    (microsoft.public.sqlserver.server)
  • Disaster Averted?
    ... Some process, unknown at this point, flooded a transaction log to the point ... the .mdf file was 0 bytes according to EM. ... Following the backup, I ... the database was now Suspect! ...
    (microsoft.public.sqlserver.server)
  • Re: Transaction Log Size
    ... We currently use a 3rd party backup agent to backup our SQL databases and ... transaction logs (Commvault Galaxy iDataAgent for SQL) and the database is ... Because we are using a 3rd party agent to backup the database, ... > here are some articles on how to shrink your transaction log. ...
    (microsoft.public.sqlserver.server)
  • Re: Transaction log problems
    ... IF you have to shrink a database or file it ... sure that you get that database backup on tape or to another machine. ... > We are using SQL Server 2000 on Windows Server 2003 Standard Edition, ... > One of the databases has recently begun showing large growth of the> transaction log and it is causing us some problems. ...
    (microsoft.public.sqlserver.server)