ReportNet 1.1, large volume, and response time.

[tbtcust]

Hi all,

I want to use ReportNet 1.1 against a DB2 database. The reports and drill troughs will return up to a million rows in a single page.

I was sold on the notion that this was not a problem and could be done with ReportNet in seconds or a couple of mins tops.

Now my Cognos consultants are saying that's not possible and we need to limit what's returned in the page to a 1000 rows or less.

o Has anyone use ReportNet 1.1 against a large data store? If so please tell of your experince.

o What obstacles did you encounter?

o How did you resolve the performance issues?

o Any performance tips

Thanks in advance for any help.

 

[KingCrab]

Kicking out a million rows is possible. However, your browser (eg IE), will take forever plus one day to render the report. Don't even think about scrolling through it.

Now for my 2 cents,
Returning a million rows is meaningless. There is no value in looking at a million of anything unless you have some kind of photographic memory and the ability to aggregate those million rows in your head. I suggest rethinking the report specs to add value to the report.

Aggregating a million rows into a couple very meaningful rows is very doable in "seconds".

 

[tbtcust]

KingCrab,

We using the tool to recreating the state of a market for an entire trading day to do ad-hoc analysis, hence the million records. Under other circumstances I would agree with you. In this case it's makes perfect sense.

Thanks for the advice.

 

[KingCrab]

you do ad-hoc analysis by viewing a million rows? It seems like you want to have an ETL process pull this data and place it somewhere for reporting.

Having a reporting tool pull millions of rows in order to do ad-hoc reporting doesn't make sense to me but who am I to argue it.