I'm not sure there's a way to do this through Profiler. You can run SP_WHO2 or SP_WHO2 Active on QA/SSMS query window to see what processes are running. Or try using the @@SPID function, though I've never used it.
DBCC Input_Buffer(<spid>) will give you the command that's running too.
AFAIK, SPIDs are not numbers stored anywhere in the server. They are process IDs, relevant to the thread connection a job or user is using.
I'm happy to be proven wrong, of course, but that's what I always thought of them as.
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"