The UAAR Enterprise DataLog controls access to the database through SQL Database Roles. Six roles control which tables, views, and stored procedures a specific user can access. The SQL “public” role is not granted any permissions in the UAAR Database.
Database roles can be assigned directly to Windows Domain Accounts or Domain Groups to provide integrated security. Although it is possible to access the Enterprise database through SQL Accounts, it is not recommended.
All of the Database roles can be assigned in the UAAR DataLog directly. However, these roles can also be assigned directly in the database using Enterprise Manager or SQL.
Database Roles include:
UAAR_ReadOnlyThis user has access to search for and view sales in the database but cannot execute the stored procedures that insert or update sales data.
UAAR_User
This user has access to search for and view sales and insert or update sales. In order to insert or update sales, users must also have permissions to a specific Access Group.
UAAR_PowerUser
This user has all of the same rights as the UAAR_User. In addition, the Power User has read access to additional supporting tables and views. This access is intended for users who need direct access to the database for ad hoc reporting.
UAAR_DeleteUser
This access is intended for the user who is not a BusinessAdmin user, but who needs to be able to delete sales.
UAAR_BusinessAdmin
These users have access to set up Rule Sets and the Sale Index. As part of that setup, they can control the Server Responses. This includes marking responses as approved and merging responses to clean up sale data.
The UAAR_BusinessAdmin role is also required to delete sales from the Enterprise database.
UAAR_SystemAdmin
This user has access to set up Database Roles and Access Groups. In order to set up Database Roles for new users, a SQL database user may need to be added. To accomplish this the UAAR_SystemAdmin role is granted the system role of db_securityadmin. If a domain account or group is given access to a database role and that user is not a user in the database, the system stored procedure sp_grantDBaccess is executed to grant that user access.