Preparing MS SQL Databases

If you are using MS SQL as the database management system for Policy Orchestrator, then you need to prepare your MS SQL system using the steps that follow.

Steps...

1. Start your MS SQL system.

2. Start the "Full-Text Indexing" Windows Service.

3. Enable remote connections for the database. Without this, the Configuration Manager will not be able to find the selected database.

   For MS SQL Server 2005:

   1. Go to the Configuration Tools and open the SQL Server Surface Area Configuration.
   2. In the menu item Database Engine > Remote Connection, select the setting Local and Remote Connections.

   For MS SQL Server 2008:

   1. Open the SQL Server Configuration Manager.
   2. From SQL Server Network Configuration, select 'Protocols for MSSQLSERVER'. Then select Named Pipes and TCP/IP.

4. Define a database system userA user is an instance of a User object in the Automation Engine, and generally the user is a specific person who works with Automic products. The user object is assigned a user ID and then a set of access rights to various parts of the system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and Release Manager object rights. You can manage all these centrally in the AWI user management functions. See also, Unified user management. with necessary rolesRoles in the user management functions in the AWI refer to user roles in Decision. User roles indicate what actions the user is allowed to perform, for example, a user with the role "super administrator" is allowed to work with all functions related to Decision.. You will need this regardless of whether you define the databases now or during the installation process.

   When you define an EventBase, you need to specify an MS SQL system user for the EventBase. This user needs to be defined in your MS SQL Server database. You can use the same user for more than one EventBase, but each MS SQL system user must have at least the following roles assigned to it:

   User Role	Purpose
   DBOWNER	Always mandatory. This user role is needed to complete the installation process.
   DBCREATOR	Only mandatory for creating databases during installation. This role is needed when you want to be able to create the database from within the installation process.

5. Recommendation: Define at least two databases.

   • One for the Admin database for metadata
   • One EventBase database for each data source system

   You can have the installation process create the databases, but it is recommended to prepare them beforehand in MS SQL yourself.

   Considerations for the Admin database

   For performance reasons, in a production environment, you should define a separate database user for the Admin database.

   Considerations for the EventBase databases

   Typically, you define one EventBase for each source system database. You could also define more than one EventBase for a single source system database. In this case, all EventBases are loaded with the relevant data from the source database. What you should NOT do is to have more than one source database write to the same EventBase, because then the data will be mixed and provide irrelevant results.

   If you have multiple source systems, give each database that will be used for an EventBase a unique name across your PCO environment.This will prevent unwanted data mix-ups.