SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The log file for database 'tempdb' is full


The log file for database 'tempdb' is full

Author
Message
Jpotucek
Jpotucek
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1604 Visits: 1677
Running SQL Server 2000 SP4 and I started getting these errors in my log several days ago.

The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space..
Error: 9002, Severity: 17, State: 6

Free space on the drive where the Tempdb data and log files reside is at 24GB free.

Tempdb is in Simple mode recovery

TempDB datafile is 3226240 KB with autorgow by increments of 10% (no limit) and autoshrink off
TempDB logfile is 48512 KB with autogrow by increments of 10% (no limit) and autoshrink off

Any help or guidance would be greatly appreciated!!



SQLRNNR
SQLRNNR
SSC-Dedicated
SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)

Group: General Forum Members
Points: 32932 Visits: 18560
Jpotucek (8/18/2014)


Running SQL Server 2000 SP4 and I started getting these errors in my log several days ago.

The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space..
Error: 9002, Severity: 17, State: 6

Free space on the drive where the Tempdb data and log files reside is at 24GB free.

Tempdb is in Simple mode recovery

TempDB datafile is 3226240 KB with autorgow by increments of 10% (no limit) and autoshrink off
TempDB logfile is 48512 KB with autogrow by increments of 10% (no limit) and autoshrink off

Any help or guidance would be greatly appreciated!!


Your log file for tempdb is only 47.5 MB and growing in increments of 10%. When you hit 47.5 MB of log use, you will receive that error message. The log will grow by it's 10% as many times as is needed to allow that transaction using tempdb to clear. Then the log will checkpoint and truncate.
If you want to reduce the errors being received, grow your log file to 256 MB. I would also change the growth increments to something like 32 MB or 64 MB.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Steve Jones
Steve Jones
SSC Guru
SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)SSC Guru (64K reputation)

Group: Administrators
Points: 64069 Visits: 19117
I'd agree with Jason. Enlarge your tempdb log. 47MB is small and space is relatively cheap. It's not worth these errors.

I'd probably grow to 1GB and monitor the space usage in the log. Find your peak, add a small pad and then set it to that size.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Jpotucek
Jpotucek
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1604 Visits: 1677
Thank you! turns out the Model Database has an initial size of 1MB (data) and 4mb (log) so when our Server is rebooted once a month I'm thinking that the TEMPDB is recreated with these tiny settings.. I'll change in both places.

Another related question.. last night I had a problem accessing one of the databases on this production server and the errors in the log were this:

SQL Server has encountered 931 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [E:\MYDB_Data.MDF] in database [MyDB] (7). The OS file handle is 0x00000390. The offset of the latest long IO is: 0x0000073aa66000

Transaction (Process ID 10) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

followed by this:

Error: 9002, Severity: 17, State: 6
The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space..

Do you think the 2 are related????



SQLRNNR
SQLRNNR
SSC-Dedicated
SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)

Group: General Forum Members
Points: 32932 Visits: 18560
It's possible they are related.

Big transaction, running on slow disk, and getting deadlocked.

The IO errors could also be due to the wait for the transaction log to grow.

Hard to say without knowing what the queries are that were involved in all three errors/warnings that you displayed.

The deadlocks could be related to slow IO. They could be related to bad indexes. They most probably are related to bad queries (which could cause tempdb log use, could cause slow IO etc etc).

Find the queries involved in those errors, and then evaluate them to determine the causality of the errors.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Jpotucek
Jpotucek
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1604 Visits: 1677
Thank you very much!



SQLRNNR
SQLRNNR
SSC-Dedicated
SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)

Group: General Forum Members
Points: 32932 Visits: 18560
Jpotucek (8/18/2014)
Thank you very much!


You're welcome.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search