Platform Deployment Guide › iConsole Standard Searches, Reports and Policies › Standard Searches, Reports and Dashboard › Requirements › Database Requirements › SQL Server Requirements for Dashboard

SQL Server Requirements for Dashboard

Note: These sections do not apply if your CMS uses Oracle or SQL Server 2005 Express.

To successfully install the dashboard, your CA DataMinder primary login (such as WGNUSER) must have a database user in the msdb database. This database user must already been granted the SQLAgentUserRole role. This allows it to create and schedule SQL Server Agent jobs. Specifically, your primary login needs to create and run scheduled aggregation jobs.

New CMSs

The SQLAgentUserRole role in the msdb database is granted automatically to your primary login when you install a new SQL Server CMS. However, if the Standard Searches and Reports installation failed on a new CMS, you must first clean up the database before attempting to reinstall.

Cleaning up After a Failed Installation

If the reports.msi installation fails (for example, because your primary user did not have the correct database roles), you will need to clean up your CMS database before trying to reinstall. Specifically, you will need to remove any orphaned database users (that is, users no longer associated with a login), plus any dashboard aggregation jobs and related schedules.

For example, in SQL Server 2005 Management Studio:

1. Delete any orphaned users in the msdb database. In the Object Explorer pane:
   1. Select the msdb database in the \Databases\Systems Databases branch.
   2. Navigate to the \msdb\Security\Users branch.
   3. Delete any msdb database users with the same name as the CA DataMinder primary login.

   Important! Do not delete the primary login from the \Security\Logins branch!

2. Delete any orphaned users in the master database.
   1. Select the master database in the \Databases\Systems Databases branch.
   2. Navigate to the \master\Security\Users branch.
   3. Delete any master database users associated with the CA DataMinder primary login.
3. Delete any aggregation jobs and schedules:
   1. Navigate to the \SQL Server Agent\Jobs branch and delete any DLP_Aggregation_<DB_name> jobs.
   2. Right-click the \SQL Server Agent\Jobs folder and choose Manage Schedules.
   3. Confirm that all schedules named DLP_Aggregation_Schedule_<DB_name> have been deleted.