I am looking at the activity monitor in MS SQL Management Studio 2005, and I see an entry from a login that I created, and it's using the tempdb, and the last command is always "SELECT INTO". And everytime I hit "Refresh" in activity monitor, that entry's "CPU" column goes up by like 60. The "program" of that activity is "MS SQL Management Studio."
I tried to kill that process, but it won't allow me, saying "cannot be killed". I disconnect from the database and reconnect, and that process is still there.
Is it gonna eventually crash my SQL Server because of continous activity? And is anyone familiar with this situation?
Thanks!