Create the SOA Security Manager Schema

You create the SOA Security Manager schema so that SQL Server database can store policy, key, and audit logging information.

The following warnings are displayed when running the policy store and audit logging schema files and do not affect the policy store configuration:

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.

To create the SOA Security Manager schema

Start the Query Analyzer and log in as the person who administers the Policy Server database.
Select the database instance from the database list.
Open sm_mssql_ps.sql in a text editor and copy the contents of the entire file.
Paste the schema from sm_mssql_ps.sql into the query and execute the query.
The policy and key store schema is added to the database.
Open SQLServer.sql in a text editor and copy the contents of the entire file.
Paste the schema from SQLServer.sql into the query, and execute the query.
The policy store schema is extended.
Repeat steps three and four to use the policy store as an audit logging database. Use the following schema file:
sm_mssql_logs.sql

Note: You are not required to configure the policy store to store additional SOA Security Manager data. You can configure individual databases to function as a separate audit log database, key store, and session store.

The database can store SOA Security Manager data.