The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space.

Question

Viewing 6 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Steve Jones - SSC Editor SSC Guru Points: 739545 More actions · Answer 1

IF you manually increase tempdb to 200GB or so, does it work?

rmaganti SSC Enthusiast Points: 152 More actions · Answer 2

Steve,

I haven't tried that...I guess I can use

USE master

GO

ALTER DATABASE tempdb

MODIFY FILE

(NAME = tempdev,

SIZE = say 2048MB)

GO

I may not want to go up to 200 G as I have other databases...

But can I try to shrink the database instead using

use tempdb

go

dbcc shrinkfile (tempdev, 'target size in MB')

go

dbcc shrinkfile (templog, 'target size in MB')

go

Any pros or cons to either one?

Thx,

Mag

Steve Jones - SSC Editor SSC Guru Points: 739545 More actions · Answer 3

I'd make it large and see.

Shrinking the database shouldn't matter, but it does mess up your indexes (fragmentation)

rmaganti SSC Enthusiast Points: 152 More actions · Answer 4

I did increase the size of temp (tempdb.mdf) to 10 G and I still get the same message....

Steve Jones - SSC Editor SSC Guru Points: 739545 More actions · Answer 5

364k records might be more than 10GB. Have you tried sp_psaceusde to see the size of the table?

rmaganti SSC Enthusiast Points: 152 More actions · Answer 6

Yes I did that and on sp_spaceused here are the stats

rows reserved data index size unused

table 364330 177792 KB 144152 KB33512 KB 128 KB

Added Later

I added an index on this column and the error message is gone...

Thx............