Hi, We have MOSS 2007 databases in SQL Server 2005 and the Tempdb log file size is increasing tremendously. Is that normal for MOSS 2007 application to put heavy load on TempDB and causes to increase TempDB log file size? what size of Content database (GB)can causes the Tempdb log file size increase to what size (GB)? Thanks

Crawl Operation increases TEMPDB Check this link - http://vspug.com/koning53/2008/07/09/troubleshooting-the-index-crawl-process/ SQL Server TEMPDB Autogrowth Since autogrowth will cause TEMPDB database to grow significantly anyway, this is essentially a free option. Dynamic data file extents are an expensive SQL Server operation and lead to fragmentation. When you consider that every time SQL Server is restarted, the tempdb is reset to its original size, you can see how SQL Server can spend a lot of time extending the tempdb. The tempdb size total size should be preset to 25% of the predicted size of your largest database. “Autogrowth” should remain enabled. If the tempdb data file(s) autogrow beyond your predicted size, then they should be permanently resized again taking into account maximum observed growth.Thanks & Regards, Kamlesh | Blog | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights. If you get your Question answered, please come back and mark the reply as an Answer, so others can find it. If you get helped by an Answer to someone else's question, please vote the Post as Helpful.

Thanks KSDN, The tempdb size total size should be preset to 25% of the predicted size of your largest database. Our Content database size is 16 GB. So the tempdb size should be 25% of 16 GB, which is 4GB. But here the mdf file size is20 MB but the ldf file size is 10 GB. The data file size is NOT increasing but only log file size is increasing. Is this normal or do I need to investigate what causing the tempdb log file size to increase rapidly? Thanks

"Is this normal?" - Is this a New MOSS 2007 setup? Was this behaviour happening before or it started suddenly since few days? I feel there seems to be some problem with your configuration. You may need to contact the Microsoft PSS for further investigation. Check the Space required for tempdb logging section in the below article: http://technet.microsoft.com/en-us/library/cc966545.aspx Additional Help: FAQ: How do I monitor and troubleshoot tempdb space? http://social.technet.microsoft.com/Forums/en-US/sqldatabaseengine/thread/48e90fa3-b7c0-427d-ad38-cd6764540221 Also, try raising the same query on tempdb Log file size issue at SQL Server forum here. You may get more help on your problem here: http://social.technet.microsoft.com/Forums/en-US/sqldatabaseengine/threads Thanks & Regards, Kamlesh | Blog | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights. If you get your Question answered, please come back and mark the reply as an Answer, so others can find it. If you get helped by an Answer to someone else's question, please vote the Post as Helpful.

Thanks, It's NOT a new MOSS installation. One of the share point application went live and after that the tempdb log file is increasing around 400 to 500 GB a day. Is this normal for having MOSS application? If yes, how large the tempdb can grow? Is there any jobs that I need to check on MOSS side? or need to check any MOSS configuration? Tempdb configuration is fine on SQL side.

400 to 500 GB growth in TEMPDB LOG file is very unusual. Aren't you running out of disk space! How many Users are using this system? Also, check this "Log Growing Pains" article and see if it helps you - http://www.sqlservercentral.com/articles/Log+growth/69476/ Thanks & Regards, Kamlesh | Blog | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights. If you get your Question answered, please come back and mark the reply as an Answer, so others can find it. If you get helped by an Answer to someone else's question, please vote the Post as Helpful.

~ 500 users. After reaching 45 GB (we have 50 GB disk space for tempdb), we have restarted the SQL Service to frreup the tempdb space and it's starting increasing again. any other ideas? thanks

As this problem is underlying at SQL Server, please get assistance from the SQL Server DBA. The link given in my above post can help you/DBA to further identify the cause/source. As an alternative, if feasable, then try stopping the SharePoint services and then monitor the TempDB LOG Growth. Did you raise this problem in SQL Server Forums? - http://social.technet.microsoft.com/Forums/en-US/sqldatabaseengine/threads