Re: log file for database 'tempdb' is full

Tech-Archive recommends: Fix windows errors by optimizing your registry

This is often a result of the log file needing to grow but can't grow fast
enough. If you are not always going to have plenty of free space in the
data and log files (for all dbs) you need to ensure that the autogrow is set
to a size that can grow in just about 10 seconds or less. This usually
means changing from a % to a fixed size that you know your hardware can
support in that time.

--
Andrew J. Kelly SQL MVP


"bill" <wbeatty@xxxxxxxxxxx> wrote in message
news:ys_Rf.6488$%m4.5009@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Yea, I increased the size. I would just love to know what caused this.

Thanks

"Robert Ellis" <robe_2k5@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23eZjmDGSGHA.5656@xxxxxxxxxxxxxxxxxxxxxxx
Bill,

As you have ample free disk space, perhaps you should consider
increasing the log file allocation to an appropriate size, rather than
just letting it auto-grow.
Do you have a workload on your server that uses a lot of temporary
tables?

Perhaps take a look at:
http://www.mcse.ms/archive81-2003-12-220762.html

HTH,
Robert


"bill" <wbeatty@xxxxxxxxxxx> wrote in message
news:p_YRf.20217$NS6.14773@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am running SQL 2000 SP3 on Windows 2003 server. The error is:

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.

Thanks


"Robert Ellis" <robe_2k5@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eD0qxvESGHA.1728@xxxxxxxxxxxxxxxxxxxxxxx
Hi Bill,

What version & edition of SQL Server are you using?
What platform is it installed on (Windows 2000, XP, 2003)?
Can you post a copy of the exact error message?

Thanks!
Robert



"bill" <wbeatty@xxxxxxxxxxx> wrote in message
news:jZURf.6473$%m4.5691@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I got several errors yesterday indicating the log file for tempdb was
full. The log file and data file are set to automatically grow and
there is 1.4 Tb free on the partition. Can anyone tell me why I would
get this error?

Thanks











.

Relevant Pages

  • Re: HELP on How to move database files
    ... http://www.support.microsoft.com/?id=314546 Moving DB's between Servers ... Issues When a Database Is Moved Between SQL Servers ... for SQL Server ... > What I want to do is to move the transaction log file to a different> location or even better get rid of it and create a new log file in its new ...
    (microsoft.public.sqlserver.server)
  • Re: SPS - SQL Server - LOG FILES.
    ... Detach the database _site. ... move the log file to another drive. ... >> We Deleted these .LDF files after stopping the SQL Server ON TEST ...
    (microsoft.public.sharepoint.portalserver)
  • Re: sp_attach_single_file_db
    ... Anyone worked a bit with SQL Server know that SQL Server does recovery at startup. ... SQL Server go through the transaction log and "synchronizes" the database with what happened since ... Stop sql server and rename the existing MDF to a new one and copy the ... Now execute the undocumented DBCC to create a log file ...
    (microsoft.public.sqlserver.server)
  • Re: Transaction Log suddenly became huge and database stopped working
    ... In addition to the other posts: to understand why it was difficult for you to shrink the log, you need to understand the concept of a virtual log file and also investigate the virtual log file structure in the ... We have an SQL Server 2005 on a windows 2003 webserver ... The database is set to autoshrink and also is backed up nightly. ... Microsoft Analysis Services Client Tools 2005.090.3042.00 ...
    (microsoft.public.sqlserver.server)
  • Re: is it possible to re-build index without logging?
    ... Microsoft SQL Server Storage Engine ... "Steve Lin" wrote in message ... >> Andrew J. Kelly SQL MVP ... >>> the log file run out of space. ...
    (microsoft.public.sqlserver.server)