![]() ![]() The misconception is that any ID above 50 indicates a user process which actually isn’t quite the case and whilst you’ll never find user processes using an ID that is 50 or below system processes can and often will use session IDs over 50. In my second result set we can see session IDs associated with user processes are taking up the numbers 51 to 54. ![]() The second image on the other hand contains the actual values where we can see the originating machine of any active sessions (host_name) and what application is being used (program_name) as well as the unique session ID’s and login time of the session that were available for system tasks also.Īt this point it is worth mentioning a common misconception about session ID’s. The first result set contained mainly NULL column values for the host, program and client columns which is indicative of system sessions. ![]() We can achieve this by adding a very simple where clause to our query: ![]() This returns a lot of information in terms of both columns and rows so we’ll focus on reducing the result set returned to essentially ignore any rows that relate to internal system tasks. Note that I have given the DMV an alias of ‘s’ which will help simplify our queries when we come to join to other objects. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |