Jeff Moden (12/3/2016)
Grant Fritchey (12/2/2016)
Talib123 (12/2/2016)
I would try the default trace, if your qucik enough you may get some information of what caused the files to grow and at what time.The system_health extended event session has everything the default trace has and more.
Will it display the SQL code that is causing TempDB to grow?
Not directly. You can read more about it here. However if there were processes that had waits beyond 15 seconds on latches or 30 seconds on locks (and tempdb might be in that), it records them.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning