Re: SQL010 - length of a table's record

for 7.2 Maximum row sizes

There are two maximum row size restrictions referred to in the description
of column-definition.

- The maximum row buffer size is 32766 or, if a VARCHAR, VARGRAPHIC,
VARBINARY, LOB, or XML column is specified, 32740.
- The maximum row data size is 3 758 096 383 if a LOB or XML column is
specified; this size is determined when a row is inserted or updated. If a
LOB or XML column is not specified, then the maximum row data size is 32766
or, if a VARCHAR, VARGRAPHIC, or VARBINARY column is specified, 32740.


The only work around would be to store the data in multiple tables.

I can't imagine having a DB table with "400 fields which are mostly VARCHAR and
of length 100 to 2000 each."

What the heck is this for?

While "key/value" tables are normally a bad idea, I can't help but wonder
if they'd make sense here,

Charles

On Wed, Aug 10, 2016 at 11:38 AM, Darryl Freinkel <dhfreinkel@xxxxxxxxx>
wrote:

Something I have not had to deal with before.

I have to create a table that has about 400 fields which are mostly VARCHAR
and of length 100 to 2000 each. So I get SQL0101.

I have always heard that the table sizes can go into the yoda byte sizes
but never a record length maximum.

For now I have reduced the field sizes to 50 chars to get passed the issue.

This is a V5R4 system.

Is there a work around or different way to use these huge record sizes?

TIA
--
Darryl Freinkel
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.