February 3, 2006 at 2:09 am
I have the following situation
For certain operations, despite these settings I get a message back saying that TEMPDB is full.
There are obviously some operations where TEMPDB cannot autogrow but does anyone know the specifics?
February 3, 2006 at 5:57 am
Do you see it growing by 500MB increments at all?
February 3, 2006 at 6:34 am
The problem usually isn't that the log CAN'T grow. The problem, instead, is that the log can't grow FAST or LARGE enough.
You set the growth to be 500MB. But what if the log is getting a transaction that is requiring 1 GB right now (bulk-insert or some other large transaction)? It grows 500 MB, but wait, that's not enough...the LOG IS FULL and the transaction can't complete the rest of its job because there's no more room. This occurs alot during re-indexing or defragging of indexes.
I set my logs to grow by 2000 MB (2GB). They don't grow often, but when they need to grow, there's always enough space created.
-SQLBill
February 3, 2006 at 6:47 am
So am I correct in thinking that it is if a single transaction requires a growth in excessive of current free space limits plus one expansion?
February 3, 2006 at 12:53 pm
Yes, that is the TOP reason you will see that error.
-SQLBill
February 3, 2006 at 10:42 pm
I have seen this before, the following article might shed some more light on the subject.
http://support.microsoft.com/kb/328551/en-us
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply