Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: "maximum row size" error for pr4_rule table in V4.2 installation (SQL Server)

Updated on December 29, 2004


For Microsoft SQL Server installations only :

When running the install script (< database> _install0402.sql) or the upgrade script ( < database> _upgrade0402.sql ) to create tables in the relational database during the install or upgrade process, the following error may appear:

Warning: The table 'pr4_rule' has been created but its maximum row size (8506) 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.



This is a known limitation of Microsoft SQL Server.  The message indicates that there are too many columns in the table, which is only an issue if data is present in all columns. 

This message may be ignored.  

When installed, Process Commander theoretically exceeds this limit, but in practice, the limit is not exceeded. 

Many different rule types (Rule- classes) are mapped to the pr4_rule table. The rows of the table do not each use all the columns (some rule types use some columns, other types use other columns, and some columns are used by all rule types). 

Thus, every row has unused columns, which prevents the error warned of above.

  • Previous topic Troubleshooting: "java.sql.SQLException" Name of SQL Server 2005 driver differs from SQL Server 2000
  • Next topic Troubleshooting: Commit error after exposing new column

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us