2 I can't test this theory at the moment, but based on the [most recent capture data posted to GitHub](https://gist.github.com/anonymous/4c8df0a69cf5e2bd0a0741aed8b10019), I would say that the reason that thee `<process>` node is empty is that it requires a currently running request (many of the attributes are found in `sys.dm_exec_requests` and not in `sys.dm_exec_sessions`) and without a currently running request, it can't report any details, similar to how doing an `INNER JOIN` between `sys.dm_exec_requests` and `sys.dm_exec_sessions` will exclude rows where a Session is active but is idle due to no current request.
5 >Ostensibly, this represents the uniqifier used in the non-unique clustered index. Is that the case?
3 In order for SQL Server to create a *non-unique* clustered index, a hidden "column" is added to the physical structure of the clustered index. That hidden column is known as the uniqifier, and as its name implies, provides a mechanism to ensure that every row in the clustered index is unique.