search cancel

SQL Server - XOG out project getting an error exceeding allowable maximum row size

book

Article ID: 242497

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Summary:  SQL Server - When attempting to XOG out project getting an error: Cannot create a row of size 8251 which is greater than the allowable maximum row size of 8060.  Expectation is that custom attributes will be excluded from the XOG output, which they are, but the underlying query is still pulling in all custom attributes in the query and running into the limit. 

Steps to Reproduce: 

1. Identify an environment with many custom objects as well as large text fields on the project object
2. Populate one of projects with large amount of data.
3. Attempt to XOG out that project with below argument. Expectation is that custom attributes will be excluded from the output which they are but underlying query is still pulling all custom attributes in the query and running into the limit.
<args name="include_custom" value="false"/>
4. Observe error specific to SQL Server "Cannot create a row of size 8251 which is greater than the allowable maximum row size of 8060."

Expected Results: when excluding custom attributes from the XOG output it is expected that query will not include them either.

Actual Results: when excluding custom attributes from the XOG output it is underlying query is still including custom attributes and running into SQL Server limit.

Environment

Release : 16.0.1

Component : Clarity XOG and REST API

Resolution

DE65198, Fixed 16.1.0.

Workaround: Once removed some larger fields eg objective and the project read XOG was successful.