Back up the transaction log for the database to free up some log s

I have a server with 80 GB free space. Logfile for the database is set to
autogrow (10%), unrestricted. The log file itself is right now about 25 MB.
This message can't be accurate, so I'm wondering what could cause this.
There was no activity that would cause the logfile to grow, certainly not 80
GB.
I've seen this intermittently, no standard, easily reproducible cause. In
this particular case, I was doing a defrag of the file system, and trying to
parse a query in an SSIS package.
I've googled this (of course) and found a few people who've seen similar
error messages with large amounts of free space, but nothing conclusive.
TIA
jdnIt is probably because your log file is so small and can't hold all the
transactions you are trying to put into it. That will force an autogrow. IF
the file can not grow fast enough you can get a timeout and this message.
Always keep plenty of free space in both the log and data files. And most
importantly do not turn on AutoShrink or run any jobs to shrink the files.
So grow your log file to a size that is large enough to hold all the
transactions you will do in the time period between the log backups and
leave it there. Also change the growth for a % to a fixed size of say40 or
50MB (your mileage may vary).
Andrew J. Kelly SQL MVP
"jdn" <jdn@.discussions.microsoft.com> wrote in message
news:AD74E005-810D-42E0-8704-F56C0157CD2E@.microsoft.com...
>I have a server with 80 GB free space. Logfile for the database is set to
> autogrow (10%), unrestricted. The log file itself is right now about 25
> MB.
> This message can't be accurate, so I'm wondering what could cause this.
> There was no activity that would cause the logfile to grow, certainly not
> 80
> GB.
> I've seen this intermittently, no standard, easily reproducible cause. In
> this particular case, I was doing a defrag of the file system, and trying
> to
> parse a query in an SSIS package.
> I've googled this (of course) and found a few people who've seen similar
> error messages with large amounts of free space, but nothing conclusive.
> TIA
> jdn