Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 'tempdb' is full message

Author  Topic 

pelegk2
Aged Yak Warrior

723 Posts

Posted - 2006-10-31 : 04:50:58
i am reciving this error :
quote:

MSSQLSERVER - " 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.


i am running a very big night process andsome times i get the above message i dont have contro over the tempDB size as its configured to auto=growth)
what can i do with the aboev message?
thnaks in advance
peleg

Israel -the best place to live in aftr heaven 9but no one wan't to go there so fast -:)

Kristen
Test

22859 Posts

Posted - 2006-10-31 : 04:57:59
"i dont have contro over the tempDB size as its configured to auto=growth"

In that case I reckon the disk is actually becoming full, so the next automatic database growth (of any other database that is using that drive) is going to fail, with possibly unpredictable application results!)

How big is TEMPDB getting? A couple of GB or hundreds of GB?

Can the overnight task be changed, e.g. to delete in batches, rather than millions of rows all in one go?

Kristen
Go to Top of Page

jen
Master Smack Fu Yak Hacker

4110 Posts

Posted - 2006-10-31 : 04:58:37
increase disk space?
or divide the task by batch

--------------------
keeping it simple...
Go to Top of Page

pelegk2
Aged Yak Warrior

723 Posts

Posted - 2006-10-31 : 05:46:02
the tempDB grow up to 5 GB i think
later on i run a JOB of shrink for the tempDB
a lack of DISK SPACE is seem's to be the problem
thnaks all
peleg

Israel -the best place to live in aftr heaven 9but no one wan't to go there so fast -:)
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2006-10-31 : 08:05:28
"later on i run a JOB of shrink for the tempDB"

Generally a BAD idea, and likely to corrupt your database unless you take very careful precautions - and even with those I still think it is a bad idea.

See: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=55210&SearchTerms=Shrinking%20TEMPDB

Kristen
Go to Top of Page
   

- Advertisement -