start:
log is 2 MB
daily activity increase it to 3MB
backup, log remains at 3MB but is empty
daily activity increase it to 45MB*
backup, log remains at 45MB but is empty
daily activity = 3MB*
backup, log remains at 45MB but is empty
* typically a lrage update or insert of data causes this
So the log size is 45 MB, and it will always use that space for the
fist 45 MB of logged transactions, and increase if it has to, but
nothing ever shrinks it.
There may be a better way, but a qucick scheduled template to check
the size after the backup and alert you via email when it is larger
than XMB, can be an alert for you to shrink it.
Dan
----- Original Message -----
From: David Koehler <[EMAIL PROTECTED]>
Date: Mon, 09 Aug 2004 11:49:32 -0400
Subject: Re: Transaction Log Size
To: CF-Talk <[EMAIL PROTECTED]>
So, they should be "shrunked"?
Dave
>They get cleared, not removed, but the problem is they are not shrunk,
>which is why they tend to get blown out of size.
>
>Dan
>
>
>----- Original Message -----
>From: Samuel R. Neff <[EMAIL PROTECTED]>
>Date: Fri, 6 Aug 2004 16:36:38 -0400
>Subject: RE: Transaction Log Size
>To: CF-Talk <[EMAIL PROTECTED]>
>
>The transaction logs get removed when you do a backup ('cause they're no
> longer needed).
>
> Sam
>
>
>
> > -----Original Message-----
> > From: David Koehler [mailto:[EMAIL PROTECTED]
> > Sent: Friday, August 06, 2004 4:33 PM
> > To: CF-Talk
> > Subject: Transaction Log Size
> >
> > Some of our transaction logs are getting very large. I know I
> > can set the database recovery model to simple and not have
> > any logging, but is there a way to actually reduce the
> > already massive log file size?
> >
> > Thanks in advance,
> >
> > dave________________________________________________________________
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
