Check SQL Server logins for auditing
An audit installation requires at least two Microsoft SQL Server databases: one for the management database and at least one for the first audit store database. To successfully connect to these databases, you must ensure that the appropriate users and computers have permission to read or to read and write for the databases that store audit-related information.
The simplest way to manage SQL logins for auditors and administrators is to do the following:
- Ensure you have a SQL login account for the NT Authority\System built-in account.
- Add the NT Authority\System account to the system administrator role.
- Use Audit Manager to grant Manage SQL Logins permissions to the Active Directory users and groups that require them.
If you use Audit Manager to manage SQL logins, you can use Active Directory membership to automatically add and remove the permissions required for auditing activity. There is no requirement to use the SQL Server Management Studio to manage logins or permissions. Because it is recommended that you have a dedicated SQL Server instance for auditing, giving the NT Authority\System account a SQL login and system administrator role is an acceptable solution for most organizations.