0 vote
Is is possible in the Enterprise Version to write connection logs just like the local connection log on the SQL server and provide a field for the user name. This would allow for auditing connections if needed without having to go to each client. It would also prevent users from clearing the logs.
Hi,
This is on the top of my list for the version after the version 5.6 (already in beta)
Thank you for your comment
David Hervieux
Devolutions inc.
David Hervieux
I noticed that there is a table called dbo.ConnectionLog, but it doesn't seem to be complete. Could this be because a lot of my users are still using 5.6?
If this is the case, on the server side, can I restrict users from using the older version?
Hi,
For now there is now way to block older version. I will try to find a solution soon.
David Hervieux
that would be excellent - as it is now, someone can easily circumvent the logging by using an older version
thank you very much for your efforts!
edited by sbonilla on 3/17/2010
Yes,
For now it more an information view than an auditing view but with the version validation, it will be now possible to enforce the security.
David Hervieux