Mar 14, 2017 - 04:35 AM
i came across the session high water mark while analysing the ReviewLite script used by LMS for auditing, but no user high water mark.
The version 15.1 of ReviewLite (August 2014) generates 10 output files; 1 of the files contains "_license.csv", that's where u can find the "session_high_water" which indicates the total number of distinct connections to the DB analysed by the script. You can check the details of the recorded sessions on the output file ending with "_session.csv".
the number of sessions doesnt really correlate to the number of users connecting to your DB if you are using generic accounts for administrators or projects or applications or any other internal use, which i encounter very often with my customers.
I believe LMS use this information as an "indication" of the minimum of users connected but not the actual number of users needed for your NUP licensing.
i am afraid i didn't yet seen an audit on NUP licensing basis, so i don't know how LMS proceeds exactly. But i imagine that they would request the list of users and their Syetem IDs (which is reported in the output files) and they would check for any generic accounts, and would then request the list of all users enabled for each generic account.
i hope that helps