: Please correct me if am wrong, we are talking here about the issue with : several individual licenses that cannot be used together with the same : management console. Right? No. I am auditing two databases on the SAME server. When I upgraded to the 3.0 version several months ago, I got the nag screen about being of of compliance. Upon inquiring, I was told that the license is per DATABASE instance. So, I purchased the additional 'seat'. A new registration key was sent. The nag screen still showed. When I reported that, I was told that the coding only recognized the 5 or 10 seat keys and to ignore the error message and a fix would be forthcoming. That was several months ago now and apparently, it still has not been addressed. It only matters when being audited for Sarbox, etc. since it shows in the event logs and when they would like to 'look over your shoulder' when you run the audit report. We are audited 4-6 times a year by PWC and KPMG as well as other independent management testing and it has to be explained each time and each time it still continues to be written up. Sorry for being long winded. Hope that helps to explain. If you'd prefer, we should likely continue this via email. Thanks.
|