Installation and Upgrade Guides › Policy Server Installation Guide › Configuring SiteMinder Data Stores in a Relational Database › How to Configure a SiteMinder Data Store in a SQL Server Database › Create a SQL Server Database With SiteMinder Schema › Create the SQL Server Database for the Policy, Key, Logging, or Session Data Stores

Create the SQL Server Database for the Policy, Key, Logging, or Session Data Stores

If the Policy Server is installed on a UNIX system, copy the following SQL Server files from the siteminder_home/db/SQL directory to a temporary directory on a Windows system:

• sm_mssql_ps.sql
• sm_mssql_ss.sql
• sm_mssql_logs.sql
• smsampleusers_sqlserver.sql

In addition, be sure that the SQL Server database server is installed on the Windows system. If the Policy Server is on a Windows system, you can run these schema files from the siteminder_home/db/SQL directory.

Run the sm_mssql_ps.sql, sm_mssql_logs.sql, and sm_mssql_ss.sql scripts to create the following SiteMinder data in a single SQL Server database:

• policy store
• key store
• logging database
• session store

To run the scripts

1. Be sure that the SQL Server database instance that is to store the SiteMinder data is accessible from the Policy Server host system.
2. Using the SQL Server Enterprise Manager, create the database instance for the SiteMinder data store.

   Example: smdatastore.

3. Create the SiteMinder schema in a single SQL Server database:
   1. Open sm_mssql_ps.sql in a text editor and copy the contents of the entire file.
   2. Start the Query Analyzer and log in as the user who administers the Policy Server database information.
   3. In the Query Analyzer, select the database instance you created using the SQL Server Enterprise Manager from the database list at the top-middle of the screen.
   4. Paste the schema from sm_mssql_ps.sql into the query.
   5. Execute the query.
4. Import the sm_mssql_logs.sql or sm_mssql_ss.sql scripts into the same database instance by following the procedure you used for the sm_mssql_ps.sql script.

You can also store SiteMinder data in a separate SQL Server database by running each script separately to create a separate:

• policy store
• key store
• logging database
• session store
• sample users database

When running the sm_mssql_ps.sql or sm_mssql_logs.sql scripts to create SQL Server–based policy or logging stores, the following warnings are displayed:

Warning: The table 'smvariable5' has been created but its maximum row size (8746) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

Warning: The table 'smodbcquery4' has been created but its maximum row size (64635) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

Warning: The table 'smaccesslog4' has been created but its maximum row size (9668) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

These warnings are expected and do not cause any problems with the policy store or logging database.

More Information:

Create the SQL Server Database Schema For Logging