If you have a situation where the tempdb is full then you can normally bind your login to the sa_tempdb or equivalent, here are the steps on how to do this:

– Do a select * from sysdatabases to see if there are any extra tempdb’s configured, if there aren’t any then you can easily create one as follows:
create temporary database to_tempdb on =’50M’ log on =’50M’

– Bind your elevated login to the extra tempdb with:
sp_tempdb ‘bind’, ‘LG’, zec3yit, ‘DB’, sa_tempdb, NULL, ‘soft’;

– Then log out and back in again and you should be able to do sp_who and other stored procs again.

– To try to clear the tempdb look for long running transactions and kill them:
select * from master..syslogshold

– You can also try to abort all transactions in log suspend on the tempdb with this command:
select lct_admin(“abort”, 0, 2)