In case you missed it before:
" Does your query use the LIMIT keyword? This is an internally hardcoded limit
that was increased, IIRC, in 7.3.6 to 250."
On further checking, here is the issue, along with fix version. I suggest you
update to the latest UDT version.
UDT-4284 -> Request for UniQuery hard limit of 150 attributes (in LIST or
REFORMAT commands) to be increased
A change was made to increase this to 250 attributes in 7.3.5. The actual
limit has now been added to the report from the LIMIT verb so you can see
limitation as "U_ATTRLIST"
As a note, limitations on number of columns isn't just an MV issue. MS SQL will
prevent you from even creating tables with large amounts of columns, whereas MV
just limits the active querying of so many at a time, so before deciding to
move because of something like that, you should really look into how the issue
is explained to management.
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jeffrey Butera
Sent: Monday, March 03, 2014 1:34 PM
To: U2 Users List; jscha...@gmail.com
Subject: Re: [U2] Reporting Tools
On 3/3/14, 3:21 PM, Jeff Schasny wrote:
> What I think many of us are suggesting is essentially "if it hurts
> when you do that, don't do that" i.e. if the query language won't
> accomplish what you want to do, use something else.
Believe me - I hear you (and others). But my administration isn't listening
because they all think this is a reasonable request ("excel
can handle 200+ columns"). So if I can't make this work in Unidata
I'll have to move to MSSQL which I really, really, really don't want to do.
At this point I'm just trying to understand the limit on the number of fields
in a LIST statement. I know in my case that it's not a sentence length issue
as I might've thought earlier so I'd like to know what is causing this (with
the understanding that I very well may not be able to solve this).
> jeffrey Butera wrote:
>> On 3/3/14, 2:58 PM, Brian Leach wrote:
>>> Try mvQuery, that should not have any problems with those volumes.
>> Hi Brian
>> We've isolated the problem to Unidata itself, not the reporting tool.
>> In short, when we do a LIST with about 150 fields, it throws:
>> "too many items in LIST"
>> As soon as we erase a field (any field), the LIST statement runs
>> properly. Unfortunately, I cannot locate any parameter that might
>> control this. I thought we were hitting U_SENTLEN - but we're
>> nowhere near that value.
Jeffrey Butera, PhD
Associate Director for Application and Web Services Information Technology
U2-Users mailing list
U2-Users mailing list