While I caught myself re-engineering the functionality of sp_who / sp_whoisactive using the sys.sysprocesses and sys.dm_exec_session views, to get an overview about running sessions and transactions on my server, I thought: "no, instead use something already that is available and tested!"
exec sp_whoisactive @get_additional_info = 1;
returns an additional XML column that offers lots of information, one of this is the Isolation Level.
I would like to have the isolation level in the primary resultset of sp_whoisactive. Did anyone have the same requirement and already solved it? Why is it not included in the primary resultset from scratch, since it is an important information.
Best Answer
Using the built-in functionality of sp_whoisactive to return the schema of the result set, you can store that information in a temp table and then use
CROSS APPLY
to extract out one or more xml nodes from the additional information