There is an has a total size limitation. it's not directly related to the number
of columns, moreso their sum total size.

re:
http://businessintelligence.ittoolbox.com/groups/technical-functional/brio-l/too\
-many-columns-to-retrieve-error-1313830

Overall, a single row can contain no more than 32K bytes of data, no matter how
many columns you select. So, you could select 32 columns of 1024 bytes each, 64
columns of 512 bytes each, 16 columns of 2K (2048 bytes) each, and so on. Any
time the calculated sum of all the columns in the query exceed 32K, this message
will pop up. It is indirectly related to the number of columns requested,
therefore.

This calculation is based on the potential length. So, let's say the
table contains a lot of varchar(2000) columns. But the actual data in
those columns is known to never exceed 50 bytes. A user could find that column
in the data model, edit its properties, and change the length. Then, the
calculated total would become less, allowing the same number
of columns to be selected that previously gave this message.

Note also that a user could change this length, even though the actual
content does run up to 2000 bytes, to be something less. The net effect of this
will be to truncate the data down to the user-entered length. This may also be
perfectly acceptable in some situations.


--- In briousers@yahoogroups.com, "Jai" <angelsdesirein@...> wrote:
>
> Anyone have idea about how many numbers of columns we can process at a
> time from a query on server? I have a query section which have 110
> columns which i am able to process successfully and the time i pull
> another column in request item it throws me an error "Too many columns
> to retrive" on server (Same happens when i run from local machine). On
> which factors it depends?
> Is it related to OCE connection on server ie Buffer size etc.
> I am getting this error in Hyperion Interactive Reporting.
>