Hi,

What is the recovery model of your TempDB? Default is SIMPLE, and it should be. Autogrowth of 10% is not the best option.

Citing Erland:

Do you have any databases that uses any form of snapshot isolation? You can see how much space the version store takes up in this DMV: sys.dm_db_file_space_usage.

you should have control over these stuff...

TempDB databases have to have more files on busy systems. And as yours rises quickly then you'd better add more (maybe will have to extend the storage for tempdb). There are many recommendations for them, and some are:

- Starting with number of files = 1/4 of CPU cores and then monitor the tempdb and see the need for addition of more. Consider the trace flag 1118 (What is Paul's recommendation for using trace flag 1118? Everyone should turn it on, on all instances of SQL Server, from SQL Server 2000 onwards. There's no down-side to having it turned on - http://www.sqlskills.com/blogs/paul/misconceptions-around-tf-1118/)

- Once I applied this nice article: https://www.simple-talk.com/sql/database-administration/optimizing-tempdb-configuration-with-sql-server-2012-extended-events/ and I got very good results.

You should invest quite a lot time on your tempdb, it's important.

Regards

IgorMi