Installation and Upgrade Guides › Policy Server Installation Guide › Prerequisites for Running Reports Using Crystal Reports › How to Configure the Policy Server for Crystal Reports › Create the SQL Server Database Schema For Logging
Create the SQL Server Database Schema For Logging
You may have already created a SQL Server logging database when you created the SQL Server database with SiteMinder schema. If you already created a logging database, do not run sm_mssql_logs.sql again as it will overwrite the current database with a new one.
If you are using SQL Server to store reports information, run the sm_mssql_logs.sql script to create a schema for logging. If there is no schema in the database to log data, reports will not work. This script is included in the <siteminder_installation>\db\SQL directory.
- siteminder_installation
-
Specifies the installed location of SiteMinder.
To create the SQL Server database schema for logging
- Make sure the SQL Server database that will contain the SiteMinder logs data is accessible from the Policy Server machine.
- Using the SQL Server Enterprise Manager, create the logs database instance.
- Create the SiteMinder schema in the SQL Server database:
- Open sm_mssql_logs.sql in a text editor and copy the contents of the entire file.
- Start the Query Analyzer and log in as the user who administers the Policy Server database information.
- In the Query Analyzer, select the logs database instance from the database drop down list at the top-middle of the screen.
- Paste the schema for logging from sm_mssql_logs.sql into the query.
- Execute the query.
- Create the SQL Server database schema for stored procedures.
Note: The 6.x Policy Server's services (Policy Server and OneView Monitor) start even if they are unable to connect to the audit logs database.
More Information:
Create the SQL Server Database Schema For Stored Procedures