PM00243: Warning regarding the RqRequirements table when running the tabl es and indexes.sql script against SQL 2000

APAR status

• Closed as Permanent restriction.

Error description

• Per RFE: RATLC01236543 - a customer has requested to change the
  datatype for the RequirementText field to be nvarchar instead of
   varchar.
  
  This RFE was delivered in the tables and indexes.sql script inst
  alled with 7.1.0.2
  
  The affected line in the script is:
  REQUIREMENTTEXT nvarchar(4000) Null ,
  
  When the script is ran against a SQL 2000 database, the followin
  g warning is provided:
  
  'Warning: The table 'RQREQUIREMENTS' has been created but its ma
  ximum row size (10075) exceeds the maximum number of bytes per r
  ow (8060). INSERT or UPDATE of a row in this table will fail if
  the resulting row length exceeds 8060 bytes.'
  
  The same script works successfully with SQL 2005.
  
  As a work-around, if the RequirementText field is changed to:
  
  REQUIREMENTTEXT varchar(4000) Null ,
  
  the script runs successfully in SQL 2000.
  

Local fix

Problem summary

• Per RFE RATLC01236543 - a customer has requested to change
  the datatype for the RequirementText field to be nvarchar
  instead of varchar.
  
  This RFE was delivered in the tables and indexes.sql script
  installed with 7.1.0.2
  
  The affected line in the script is:
  REQUIREMENTTEXT nvarchar(4000) Null ,
  
  When the script is ran against a SQL Server 2000 database,
  the following warning is provided:
  
  "Warning: The table 'RQREQUIREMENTS' has been created but
  its maximum row size (10075) 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."
  
  The same script works successfully with SQL Server 2005 and
  2008.
  
  As a workaround, if the RequirementText field is changed to
  REQUIREMENTTEXT varchar(4000) Null ,
  
  the script runs successfully in SQL 2000.
  
  This issue is easily reproduced when using the scripts that
  are provided with ReqPro 7.1.0.2 and a SQL 2000 database.
  
  Attached is the tables and indexes.sql script (that is
  provided with ReqPro 7.1.02 out of the box)
  

Problem conclusion

• No plan to fix. A workaround is available by manually
  changing the datatype for the REQUIREMENTTEXT field from
  NVARCHAR(4000) to VARCHAR(4000) in case multilangual support
  is not required in SQL Server 2000.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels