Re: why does my transaction log fill very fast?

From: Dan Guzman (guzmanda_at_nospam-online.sbcglobal.net)
Date: 11/17/05 

Date: Thu, 17 Nov 2005 06:11:42 -0600

Cross-posting to microsoft.public.sqlserver.server.

All database changes are written to the transaction log. The before/after
image of each row is the stored for fully-logged statements like INSERT,
UPDATE, DELETE. With minimally-logged operations like TRUNCATE TABLE, only
allocation information for the affected extents are recorded.

It is unusual for a web application to require a large transaction log since
OLTP apps generally consist of relatively small transactions. This might
indicate an application problem such as inadvertently modifying more data
than intended or long-running transactions. 

-- 
Hope this helps.
Dan Guzman
SQL Server MVP
"Manish Sukhija" <ManishSukhija@discussions.microsoft.com> wrote in message 
news:DDC47FD3-602B-4DC1-8253-523807C71DEA@microsoft.com...
> Hi All,
>        one of my web application fills its transaction log very fast, as
> database is on live server and some other company takes care of it's
> database, so i'm not able to shrink it's log. According to them, 
> transaction
> log is to be truncate several time in a day automatically. now i don't
> understand how this transaction log fills so much fast? any idea?

Relevant Pages

  • RE: SPS 2003 transaction log question
    ... It is a SQL question, ... you truncate the sql transaction logs ... set the recovery model of the database to “Simple”. ... This truncates the transaction log. ...
    (microsoft.public.sharepoint.portalserver)
  • 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)
  • RE: Backup in maintenance plan
    ... I selected "Back up the transaction log of the database as part of the ... To ensure an efficient and effective backup and recovery strategy for your ... The transaction log should not be backed up if the truncate log on ...
    (microsoft.public.sqlserver.programming)
  • RE: Shrink File?
    ... As my understanding of you problem, you have a database with a data file ... in the log file. ... You can truncate only nonactive portion of the transaction log. ...
    (microsoft.public.sqlserver.setup)
  • RE: Event log error message: Database log truncated: Database
    ... First of all, this is NOT an error message, it is an Application Event log ... The message says that the System explicitly truncated the transaction log. ... Depending on your current database recovery mode setting, ... Create a Full backup immediately after a truncate log action. ...
    (microsoft.public.sqlserver.server)