SQL permissions
UNICOM Intelligence Interviewer - Server Admin users need sufficient permission to access the SQL databases used by UNICOM Intelligence Interviewer - Server Admin and UNICOM Intelligence Interviewer - Server Admin in order to carry out their work, without compromising the overall security of your site. When you install UNICOM Intelligence Interviewer - Server Admin and UNICOM Intelligence Interviewer - Server Admin, the installation procedure sets up default permissions which are generally adequate for most users. You may change these permissions if you want, but you must be aware that certain minimum permissions must exist otherwise activities will not have the access they require to the data. These permissions are listed below.
Note Unless otherwise stated, these permissions apply to the Anonymous Access User that you created before installing UNICOM Intelligence Interviewer - Server Admin.
DPM
SELECT, INSERT, UPDATE, DELETE on the ProjectMgmt table in the mrInterviewData database.
UserAuth
DELETE, INSERT, UPDATE, SELECT on Users, Roles, UserRoles, and UserTickets in the mrUserData database.
Sample Management
DPM server account needs SELECT, INSERT, UPDATE, DELETE on the sample database.
mrActivate
The code is run using the DPM server account, so these permissions should be appended to the ones shown earlier for DPM.
For project database creation
CREATE DATABASE on the user's default database.
EXECUTE for stored procedure SP_GRANTDBACCESS on the project's database.
EXECUTE for stored procedure SP_ADDROLEMEMBER on the project's database.
For browsing Sample Management databases
EXECUTE for stored procedure SP_DATABASES on the user's default database.
EXECUTE for stored procedure SP_TABLES on a Sample Management database.
SELECT on a Sample Management table.
Quota
The process running the Quota system needs to be able to create tables, views, and stored procedures and to have read, write, and execute permissions on the quota objects.
Making an UNICOM Intelligence Interviewer - Server Admin case data (RDB2) database
Normally, the schema for the RDB2 database is created during activation (see above) but a user may need to create a database for export, for example.
When schema creation is required, the user needs permission to create tables and stored procedures in the database. The user will also need permission to create a new role and to grant permissions to that role.
Access to RDB2 data
Connecting users should be members of the SPSS_MR_DataModel role, which is assigned the privileges required for reading from and writing to the RDB2 database.
SPSS_MR_DataModel needs the following permissions:
SELECT, UPDATE, INSERT, DELETE on SQL_SCHEMA_VERSION_TABLE.
SELECT, UPDATE, INSERT, DELETE on SQL_VARIABLES_TABLE.
SELECT, UPDATE, INSERT, DELETE on SQL_RESPONSES2_TABLE.
SELECT, UPDATE, INSERT, DELETE on SQL_OTHERDATA2_TABLE.
SELECT, UPDATE, INSERT, DELETE on SQL_RESPONSE_SERIAL_.
EXECUTE on SQL_SP_RESERVE_RESPONSE_SERIAL.
EXECUTE on SQL_SP_RESERVE_RESPONSE_SERIAL_EX.
Participants
CreateDatabase permission in order to create new sample databases.
See also