March 13, 2007 at 11:53 am
I have database runiing on sql 2000/sp4 .The size of the databse is 10G.
Temp DB is becoming very huge upto 40 GB. I find out the temp DB is not doing checkpoint.
How can i make Temp db to do check point. As a temp fix i create the sql job which
is doing dbcc srink file every 5 minutes.How can i make temp db to do check point??
Thanks
Hammad
March 13, 2007 at 5:41 pm
Temp dm should be in simple mode-- Why is it growing this fast? If you application requires huge temp space then you should partition your tempdatabase etc...
Hope this helps
March 16, 2007 at 11:00 am
Correct me if I'm wrong, but isn't the tempDB only resized at start up? Your queries are probably doing a bunch of sorts which is filling up your tempdb.
If it is the tempdb log file that is filling up then change it to the simple recovery model and that should help.
read the following article for the highlights of the tempdb
http://www.microsoft.com/technet/prodtechnol/sql/2005/workingwithtempdb.mspx
Marvin Dillard
Senior Consultant
Claraview Inc
March 17, 2007 at 10:31 am
As some have suggested, step 1 would be to ensure the Recovery Mode on TempDB is set to SIMPLE.
Step 2 would be to rewrite your code so it doesn't use the pot wad of cursors I think you're probably using... the following references are mostly for SS2005 but a good abount of the information applies to 2k, as well.
http://msdn2.microsoft.com/en-us/library/ms345368.aspx
http://msdn2.microsoft.com/en-us/library/ms190768.aspx
http://msdn2.microsoft.com/en-us/library/ms175527.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
March 19, 2007 at 3:10 am
Looks like the bug described in the following KB article:
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply