We have a siutation in SQL Server where tempdb gets full. Is there a way in Performance Analysis that we can identify which SQL or Stored Procedures cause the space issue in tempdb?
If you know when it is occurring, you should be able to select that time range, then drill down on the tempdb database and find the most active SQL statements during that time.
For example, on the History screen select the appropriate time range, then go to Instance View | Databases | tempdb | SQL Statements. You can also choose "TSQL Batches" instead of "SQL Statements" if you prefer, or focus on DB Users, etc.
When you drill down to Instance View | Databases | tempdb | SQL Statements it is showing only the SQL statements that pertain to the tempdb instance. The most active statements here would be the most likely culprits causing the problem