tempdb log full

[Tom]

I received an error that the log in tempdb was full, but the log and
data segments are set to automatically grow with no limit AND there is
plenty of available space on the disk. So I don't understand why this
error occurred. Does anyone have any ideas?

Thanks,

Tom

[John Bell]

Hi

Did this say it was full or could not grow? If the latter check out how the
amount of disc space available. You may also want to review how you are
using tempdb.

John

"Tom" <zi**********@bloglines.com> wrote in message
news:5b*************************@posting.google.co m...

I received an error that the log in tempdb was full, but the log and
data segments are set to automatically grow with no limit AND there is
plenty of available space on the disk. So I don't understand why this
error occurred. Does anyone have any ideas?

Thanks,

Tom

[Erland Sommarskog]

Tom (zi**********@bloglines.com) writes:

I received an error that the log in tempdb was full, but the log and
data segments are set to automatically grow with no limit AND there is
plenty of available space on the disk. So I don't understand why this
error occurred. Does anyone have any ideas?

Do you have tempdb set to autoshrink? In this case, if tempdb grows
because of a wild transaction, the log will shrink once the wild
transaction is rolled back, because it ran out of disk space for
the log.

Another possibilty is that even if there is plenty of disk space, it may
not be plenty enough. 150 MB may seem plenty, but if the tempdb log
is 2 GB, and autogrow is set to the default 10%, autogrow will fail.
--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp