Creating a custom SQL database and user for Symantec Endpoint Protection Manager 11

Article:TECH104988  |  Created: 2008-01-22  |  Updated: 2012-07-13  |  Article URL http://www.symantec.com/docs/TECH104988
Article Type
Technical Solution


Issue



You want to create a custom Microsoft SQL database and user before installing Symantec Endpoint Protection Manager (SEPM) 11.x.


Solution



Note: This procedure is optional when installing of the Symantec Endpoint Protection Manager (SEPM). The SEPM installer will create the necessary database and user during installation. This procedure should only be followed in environments where database rights and permissions are tightly controlled, or highly customized database settings are required.

 

Requirements

  • Using Microsoft SQL server with Symantec Endpoint Protection Manager (SEPM) requires an existing instance of Microsoft SQL Server.
  • If the SQL server is installed on a different computer than the SEPM, install SQL client components to the SEPM computer.


Creating a custom SQL database

  1. Open the Microsoft SQL Server Management Studio and log in to the target SQL instance as an sa equivalent user.
  2. Right-click on the Databases folder in the Object Explorer pane and choose New Database.
  3. Configure the following settings in the New Database window:
    1. Enter the desired database name in the Database name field (e.g. sem5).
    2. Create 4 new database files by clicking Add 4 times. Make the following configurations:
      1. On the first newly created file:
        1. Enter "<database>_content" in the Logical Name column (e.g. sem5_content).
        2. Click the drop-down box in the Filegroup column and choose <new filegroup>.
        3. Enter "FG_CONTENT" into the New Filegroup dialog and click OK.
      2. On the second newly created file:
        1. Enter "<database>_index" in the Logical Name column (e.g. sem5_index).
        2. Click the drop-down box in the Filegroup column and choose <new filegroup>.
        3. Enter "FG_INDEX" into the New Filegroup dialog and click OK.
      3. On the third newly created file:
        1. Enter "<database>_loginfo" in the Logical Name column (e.g. sem5_loginfo).
        2. Click the drop-down box in the Filegroup column and choose <new filegroup>.
        3. Enter "FG_LOGINFO" into the New Filegroup dialog and click OK.
      4. On the fourth newly created file:
        1. Enter "<database>_rptinfo" in the Logical Name column (e.g. sem5_rptinfo).
        2. Click the drop-down box in the Filegroup column and choose <new filegroup>.
        3. Enter "FG_RPTINFO" into the New Filegroup dialog and click OK.
      5. Optionally specify a custom Initial Size and Autogrowth settings for the Filegroups configured above.
  4. Click Options>Recovery model and choose Simple.
  5. Click OK create the new database. This may take several minutes.


Creating a custom SQL login for the database

  1. Open the Microsoft SQL Server Management Studio and log in to the target SQL instance as an sa equivalent user.
  2. Expand Security in the Object Explorer pane.
  3. Right-click on Logins and click New Login.
  4. Enter the desired name in the Login name field.
  5. Configure the Authentication settings:
    1. Select the SQL Server authentication radio button if you do not require Windows Authentication.
      1. Provide the SQL authentication password and password confirmation.

        Note: The password may contain the characters ~#%_+=|:./ but not the characters `!@$^&*()-{}[]\\<;>,?
      2. Uncheck user must change the password at next login.
    2. Select the Windows authentication radio button if you require Windows Authentication.
  6. Select the SEPM database from the Default database drop-down box (e.g. sem5).
  7. Click the User Mapping page.
    1. Check the SEPM database (e.g. sem5) on the Users mapped to this login section.
    2. Check db_datareader, db_datawriter, and db_ddladmin in the Database role memberships section.

      Note: Do not uncheck public.
       
  8. Click OK to create the user.

Supplemental Materials

Value1290264

Legacy ID



2008052215175648


Article URL http://www.symantec.com/docs/TECH104988


Terms of use for this information are found in Legal Notices