Overview

This article provides an answer to the query: What SQL database roles are required for the user configured in GFI EventsManager?

Environment

EventsManager 2011 and older

Process

In order for GFI EventsManager to create, update and modify the database which is used to store the GFI EventsManager data, the user that is being used to connect to the database must have a db_owner role on the database. The rest of the article explains how to create a new SQL user and assign the db_owner role to the user:

1. Open SQL Server Management Studio.
2. Log in with your SQL Administrator account.
3. Expand the 'Security' folder.
4. Right-click on the 'Logins' folder and select New Login.
5. Enter the login name for the SQL user. You can also select a Windows user at this stage and continue with Windows Authentication.
6. If you want to use SQL Server Authentication, select 'SQL Server authentication' and enter the password for the new user.
7. Remove the option 'Enforce password expiration'.
8. If you have already created the GFI EventsManager Database, perform the following:
   1. Click on the User Mapping Node.
   2. Tick Map for the GFI EventsManager database.
   3. Tick db_owner for the Database Role Membership.
   4. Click OK to save changes.
9. If you still have not created the GFI EventsManager Database and wish to create it with the GFI EventsManager SQL user, perform the following:
   1. Click on the Server Roles tab and tick the dbcreator server role. Any databases created by the user are automatically assigned the db_owner database role membership.
   2. Click OK to save changes.

The following procedure explains how to change the user being used to connect to the SQL Server by GFI EventsManager:

1. Open the GFI EventsManager Management Console.
2. Click on the Configuration tab and select Options.
3. Right-click on the 'Database Backend' node and select Change Database Backend.
4. In the Change Database tab, select the user created previously and click the Apply button to execute the changes or create the database.
5. Click OK to save changes.