RE: Lights needed on the T Log management
From: Mike Epprecht (SQL MVP) (mike_at_epprecht.net)
Date: 01/14/05
- Next message: Mike Epprecht (SQL MVP): "RE: Performance - transactions/second"
- Previous message: SB138: "hot fixes"
- In reply to: Chris V.: "Lights needed on the T Log management"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 14 Jan 2005 05:47:01 -0800
Hi
It carries on from where it last was. Once it hits the end of the file and
there is space at the beginning of the file, it starts at the beginning again.
That is why truncating a log file will not always make it shrinkable to the
smallest possible size.
Regards
Mike
"Chris V." wrote:
> Hi,
>
> I've got a quick question about the way SQL server handles the Transation
> logs (in Full recovery mode).
>
> Transations are kept in the log until the log is or backed up or truncate,
> The size will be reduce will DBCC SHRINKxxx
>
> My question is : After I truncate a log, will the next transactions be
> append to the log which will keep growing, or will the new transactions be
> written on the space which has been released by the truncation ?
>
> Thanks
> Chris
>
>
>
- Next message: Mike Epprecht (SQL MVP): "RE: Performance - transactions/second"
- Previous message: SB138: "hot fixes"
- In reply to: Chris V.: "Lights needed on the T Log management"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
