Log file growth

Is there any way to find out the last time a log file grew? Perhaps a log
that SQL Server keeps?
TIA
CarySQL Server doesn't keep that info by default. You can trace that event using Profiler...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Cary" <Cary@.discussions.microsoft.com> wrote in message
news:39AC150F-3145-4EE5-B5BF-633B604D82C9@.microsoft.com...
> Is there any way to find out the last time a log file grew? Perhaps a log
> that SQL Server keeps?
> TIA
> Cary|||Transaction logs will grow with every insert, update, delete, or other change
to the database.
There are tools that allow you to kinda read them, but if you're just
looking for a general idea you can look at the date/time stamp on the actual
.LDF file (which is the actual transaction log) and that should provide you
with an idea of when it last changed.
"Cary" wrote:
> Is there any way to find out the last time a log file grew? Perhaps a log
> that SQL Server keeps?
> TIA
> Cary|||I believe that Cary want to track the growth of the *file* size, not used space inside the file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"matt" <matt@.discussions.microsoft.com> wrote in message
news:C8424618-ED00-4A2A-A762-9BFD568BE5B4@.microsoft.com...
> Transaction logs will grow with every insert, update, delete, or other change
> to the database.
> There are tools that allow you to kinda read them, but if you're just
> looking for a general idea you can look at the date/time stamp on the actual
> .LDF file (which is the actual transaction log) and that should provide you
> with an idea of when it last changed.
> "Cary" wrote:
>> Is there any way to find out the last time a log file grew? Perhaps a log
>> that SQL Server keeps?
>> TIA
>> Cary|||Yes Tibor, that's exactly what I wanted to track. Another question on the
same note. I have a db ~5.5 GB in size with a log file ~ 350Mb in size. The
db is backed up every night and the log is truncated with that. I can see
that my log file fills up very fast during the day and is set to autogrow
which it does. Does this detrimentally impact the perfomance of the server?
That is why I wanted to know when the server actually "GROWS" the file. I
believe it is and I am getting a very high I/O rate on my log and DB drives
which is severely affecting performance. I am unsure of whether this high
I/O is the file growth or something more that is currently eluding me.
TIA
Cary
"Tibor Karaszi" wrote:
> I believe that Cary want to track the growth of the *file* size, not used space inside the file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "matt" <matt@.discussions.microsoft.com> wrote in message
> news:C8424618-ED00-4A2A-A762-9BFD568BE5B4@.microsoft.com...
> > Transaction logs will grow with every insert, update, delete, or other change
> > to the database.
> >
> > There are tools that allow you to kinda read them, but if you're just
> > looking for a general idea you can look at the date/time stamp on the actual
> > .LDF file (which is the actual transaction log) and that should provide you
> > with an idea of when it last changed.
> >
> > "Cary" wrote:
> >
> >> Is there any way to find out the last time a log file grew? Perhaps a log
> >> that SQL Server keeps?
> >>
> >> TIA
> >> Cary
>
>|||Growing definitely impacts performance and usually in a big way when it
happens. The log file does not automatically get truncated when you do a
full backup. You need a log backup for that to happen. If you are not doing
regular log backups then you should set the recovery mode to simple and you
won't have to worry about any of that. Do not shrink the file once it has
grown otherwise you will just have to grow it again.
--
Andrew J. Kelly SQL MVP
"Cary" <Cary@.discussions.microsoft.com> wrote in message
news:0E2C4E19-A16D-4601-A8C2-6544E191CFEF@.microsoft.com...
> Yes Tibor, that's exactly what I wanted to track. Another question on the
> same note. I have a db ~5.5 GB in size with a log file ~ 350Mb in size.
> The
> db is backed up every night and the log is truncated with that. I can see
> that my log file fills up very fast during the day and is set to autogrow
> which it does. Does this detrimentally impact the perfomance of the
> server?
> That is why I wanted to know when the server actually "GROWS" the file. I
> believe it is and I am getting a very high I/O rate on my log and DB
> drives
> which is severely affecting performance. I am unsure of whether this high
> I/O is the file growth or something more that is currently eluding me.
> TIA
> Cary
> "Tibor Karaszi" wrote:
>> I believe that Cary want to track the growth of the *file* size, not used
>> space inside the file.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> http://www.sqlug.se/
>>
>> "matt" <matt@.discussions.microsoft.com> wrote in message
>> news:C8424618-ED00-4A2A-A762-9BFD568BE5B4@.microsoft.com...
>> > Transaction logs will grow with every insert, update, delete, or other
>> > change
>> > to the database.
>> >
>> > There are tools that allow you to kinda read them, but if you're just
>> > looking for a general idea you can look at the date/time stamp on the
>> > actual
>> > .LDF file (which is the actual transaction log) and that should provide
>> > you
>> > with an idea of when it last changed.
>> >
>> > "Cary" wrote:
>> >
>> >> Is there any way to find out the last time a log file grew? Perhaps a
>> >> log
>> >> that SQL Server keeps?
>> >>
>> >> TIA
>> >> Cary
>>