Hi there,

Recently I ran into the following problem. I have a database with
transaction log files that are set to "automatically grow with 10%". I
was doing a data transfer which took a lot of transaction log. At first
the file grew automatically, but then the data transfer failed with the
error:

Operating system error 112(There is not enough space on the disk.)
encountered.

So the file had apparently stopped growing automatically. I finally
managed to get the data transfer through by manually adding space to
the transaction log.

Has anyone ever run into this problem and know why this happened?

Thanks in advance,

Debora

The Error Msg means exactly what is says....

The file did not grow because there was not enough free disk space.
This isn't a problem with SQL Server as such - the problem occurs
because the disk that the Log File resides on ran out of space.

No free disk space - no file growth.

HTH

Barry

Hi Barry,

Thanks for the tip, but that wasn't the case. The disk had plenty of
space left, which was proved by the fact I could add space manually to
that disk.

Debora

You can get into situations where the rate of data growth within tempdb
is greater than the rate at which SQL can increase the size of tempdb.
Just modify the size manually to encompass theoretical size required.

In my case it wasn't tempdb. In fact, tempdb wasn't used at al. Does
the same go for regular user databases?

Debora