Thank you all for your input.

According to this link - http://www.microsoft.com/technet/prodtechnol/sql/2005/workingwithtempdb.mspx#E4CAC - the features generating version-store records in tempdb are:

• Snapshot isolation

• Read committed snapshot isolation (RCSI)

• Online index build

• Triggers

• MARS

Of all these the only one we use in our SQL instance is triggers to store information on DML operations in history tables for auditing purposes.

So I think my plan will be to poll sys.dm_exec_requests at the time during which this happens (seems to be a regularly occurring process) and use "OUTER APPLY sys.dm_exec_sql_text..." to get to the actual SQL running at the time. I will store this info in a table and look for the trigger operation and the table(s) involved.

Ultimately, my goal is to get at the actual SQL that is causing this and the login/session_ID under which it is running.

What do you guys think?