Yep, and could come from a number of causes. One of the easiest to explain is that you have a Spool operation which is writing out to tempdb. Another is that you have a hash match that is too big for memory (or exceeded the estimated amount of memory needed) and is now spilling to disk. Take a look at the execution plan to understand what might be going on.