TempDB Transaction log is growing

[bessebo]

I've noticed that the transaction log associated with my Tempdb database has been growing and is now almost up to 1GB. Is there a need to truncate the transaction log of this database? I am using Full recovery mode.

 

[SQLBill]

Quickest way to empty the TEMPDB log file is to stop and restart SQL Server. Every time SQL Server is restarted, it rebuilds TEMPBD based on MODEL.

-SQLBill

Posting advice: FAQ481-4875

 

[yelworcm]

tempdb can not be put into FULL recovery mode. It should throw an error, if you try. Something else is happening. Do you have procedures that use large-ish temp tables, or long transactions?

 

[bessebo]

Thanks for everyone's response. The transaction log actually cleared itself up since I posted this. It is down to 300MB or so now.

Regards,
Bessebo