Use this procedure to create an optional non-system administrator user on the primary Avaya Control Manager SQL Server.
Procedure
Log in to the primary Avaya Control Manager SQL Server.
You must log as the Avaya Control Manager SQL Server domain user with administrative rights for all machines in the Avaya Control Manager database cluster. To check the user name, see Finding the Avaya Control Manager SQL Server domain user.
Click Start > Microsoft SQL Server > Open SQL Server Management Studio.
In the Object Explorer pane, click Connect > Database Engine.
SQL Server Management Studio displays the Connect to Server dialog box.
In the Server name field, select the local instance of SQL Server.
In the Authentication field, select SQL Server Authentication.
In the Login and Password fields, enter the system administrator credentials.
The system administrator is usually the default sa user created during SQL Server installation.
Click Connect.
In the Object Explorer pane, right-click the SQL Server instance and click New Query.
In the content pane, run the following command to create a new login:
USE [master]
GO
CREATE LOGIN <<loginName>> WITH PASSWORD = '<<password>>', CHECK_POLICY=OFF
For example:
USE [master]
GO
CREATE LOGIN csEDMLogin WITH PASSWORD = 'myPassword1', CHECK_POLICY=OFF
Run the following command to select the security identifier (SID) for the new login:
SELECT sid, name FROM syslogins where name = '<<loginName>>'
For example:
SELECT sid, name FROM syslogins where name = 'csEDMLogin'
shows SID = 0x0589627E7A96D447865135449C41E53B
Important:
Note the SID. The SID is required when setting up the secondary SQL server.
In the Object Explorer pane, click Security > Logins.
Right-click the newly created login name and click Properties.
SQL Server Management Studio displays the Login Properties dialog box.
In the navigation pane, click General.
In the Default database field, select the EDM database name.
In the navigation pane, click User Mapping.
Select the Map check box for the EDM database.
Click OK.
In the Object Explorer pane, click Databases > <EDM Database> > Security > Users.
Verify that the newly created login name is available in the list of users.
In the Object Explorer pane, right-click the EDM database and click New Query.
In the content pane, run the following commands to grant permissions to the newly created user:
GRANT SELECT, INSERT, UPDATE, DELETE ON CS_OPERATION TO <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON CS_PROVISION TO <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON GENERATED_KEYS TO <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON INTERACTION_NOTE to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON INTERACTION_PARTICIPANT to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON SERVICE_ATTRIBUTE to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON SERVICE_ATTRIBUTE_GROUP to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON ROUTING_SERVICE to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON CUSTOM_DETAIL to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON INTERACTION to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON LINK to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON TOPIC to <<loginName>>;
GRANT SELECT, INSERT, UPDATE, DELETE ON ENGAGEMENT to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON OUTCOME to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON SENTIMENT_RATING to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON TENANT to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON INTERACTION_STATUS to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON INTERACTION_SUBSTATUS to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON CHANNEL_SUBTYPE to <<loginName>>;
GRANT SELECT, INSERT, UPDATE ON CHANNEL_TYPE to <<loginName>>;
GRANT SELECT, INSERT, UPDATE, DELETE ON CS_RESURRECT to <<loginName>>;