There are many events that would necessitate users needing to be re-secured to SQL. For example, if the Service Account for GlobalSearch or GlobalCapture needs to be changed, that account will need full access to our SQL Databases.
Adding users and giving them proper permissions is easy.
Open SQL Server Management Studio and Connect to the Database Engine containing the GlobalSearch/GlobalCapture Databases
Expand the "Security" Folder in the Object Explorer
Expand the "Logins" Folder under Security
To CHANGE or MODIFY Permissions on your Service Account do the following:
Right click your service account user (Typically SSAdministrator)
Once in the Properties window, click the "Server Roles" page and ensure your Service account is both in the "Public" and "Sysadmin" Role
Click "User Mapping" - this will bring up a list of databases in your server
Ensure all GlobalSearch databases are checked and the Database Role Membership is set to "db_owner"
The system databases that need to have a secured user are as follows:
Additionally, your production or demo databases (IE - BrewHaven or Getsmart) need to be secured similarly
Hit "OK" to save your changes
To ADD a User to the Database do the following:
Right click the "Logins" folder in the Object Explorer
Click "New Login" - this will prompt the new user window
Under "Login name:" enter your user, complete with domain or local name (IE - Mydomain\myusername or firstname.lastname@example.org)
From here follow steps 4a through 4f
You will need to make these changes with a user who is a member of the "sysadmin" role. If your user cannot see the databases when logging into SQL, it's likely an issue of insufficient permissions.