s-l-o-w reports

[a0167913]

I have a report that takes 15 minutes to run in CRN.  It was built w/developer studio.   When I take the SQL for the report from the audit trail nativequery table, the SQL runs in 3 seconds.  I'm only returning 100 data rows.    I run on a unix configuration.    Cognos people swear it's a database problem. 

Can anyone suggest any Cognos documents or have any experience with settings that could spead this up?    3 seconds vs. 15 minutes is a very large time difference.

[Opher]

When you run the report in CRN, is the output in PDF format?  What version of CRN are you using?  What is the underlying database?

Regards,
Opher

[Blue]

What is "w/developer studio"?

When you take the SQL from the report (how BTW?) are you checking all the nooks and crannies for filters, slices, tuples, sub queries, etc?

The most sure way we have found to kill a report's performance is to include a tuple in the logic!

Bluey

[almeids]

I don't mean to take this on a tangent, but must ask Blue: what does "include a tuple in the logic" mean?
I've always understood that term to be a synonym for database "row" or "record".
thanks...

[Blue]

A tuple (pronounced toopul) is a new feature in Cognos 8 BI Report Studio.  It allows the designer to reference a particular intersection (cell) of a row and column in the report.  It has nothing to do with relational database terminology.

[almeids]

Could have sworn there was a button somewhere to thank people...oh, well...
"thanks, Blue!"

[Blue]

There is! On the left click on "Applaud this member's contribution". ;)