Assigning SQL permissions on remote SQL Servers - Genetec Mission Control™ 3.0.6.0

Genetec Mission Control™ Deployment Guide 3.0.6.0

Applies to
Genetec Mission Control™ 3.0.6.0
Last updated
2022-10-26
Content type
Guides > Deployment guides
Language
English
Product
Genetec Mission Control™
Version
3.0

You must have the necessary SQL permissions on the remote SQL server with Genetec™ Server services where the Incident Manager role is active.

Before you begin

Install SQL Server Management Studio (SSMS) on your system. You can download an instance from Microsoft.com.

For information on installing SQL Server on a separate drive, see the Security Center Installation and Upgrade Guide.

What you should know

Security Center offers two modes of user authentication whilst connecting to the SQL server:
Windows Authentication
Configured by default. The SQL server has the same login credentials as the Windows administrator.
SQL Server Authentication
Configure for advanced scenarios. This enables dual authentication because when you configure this option, the default Windows Authentication is also available.

Procedure

To configure dual authentication:

  1. Open SQL Server Management Studio.
  2. In the Object Explorer pane, right-click the SQL Server instance and select Properties.
    The Server Properties dialog box opens.
  3. In the Select a page pane, click Security.
  4. In the Server authentication section, select SQL Server and Windows Authentication mode and click OK.
    NOTE: For your configuration to take effect, you must restart your SQL Server.
  5. Restart SQL Server:
    1. Open SQL Server Configuration Manager.
    2. In the Sql Server Configuration Manager pane, select SQL Server Services.
    3. Right-click SQL Server (SQLEXPRESS) and click Restart.
    Dual authentication is now configured.
  6. Create a new SQL Server login using SQL Server Authentication:
    1. In the Object Explorer pane, click Security > Logins > New Login.
      The Login- New window opens.
    2. Select SQL Server Authentication.
      Tip: Remember the login credentials for your SQL server. You would require Administrator level access to reset them.
    3. Enter a login name.
    4. Enter a new password.
    5. Clear the Enforce password policy option.
    6. From the Default database list, select IncidentManagement.
    7. In the Select a page pane, select Server Roles.
    8. In the Server Roles section, select one of the following:
      public
      For Security Center versions 5.10.1.0 and later.
      dbcreator
      For Security Center versions 5.10.0.0 and earlier.
    9. Click OK.
      A new SQL Server login is created.

To test the new SQL Server login:

  1. In Config Tool, go to System > Roles > Incident Manager.
  2. On the Resources page, configure the following:
    Database server and Database
    The name for the Database server and Database must match the name found at Security > Login > New Login > Default database name.
    SQL Server login
    From the Authentication list, select SQL Server and enter the new SQL Server credentials that you created.
  3. Click Apply.
    The database is connected to the server with the new SQL server credentials.