If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

[RS]Bad Performance in Quary/Report Studio

Started by jiunshen, 03 Oct 2006 02:57:27 PM

Previous topic - Next topic

jiunshen

I installed Cognos 8 MR2 in our new Windows 2003 Server and MS SQL 2005 Server. (same box)

Everything works fine, but when I wanted to design some reports using Quary/Report Sudio it took me 2 - 3 mins to wait. It was even worse when running the reports. The records in database is not much (around 600,000.) I only used around 10 tables and within simple connections setting in Framework Manager.

Does Cognos have any tuning setting stuff, or what kind of way I should be aware?

Thanks for your answer and time,
Samuel

redstang

How long does your query run outside of RS?  I.E. if you take the sql and run it elsewhere, how long does it take?

Also, do you have C8 set up to use Active Directory?  We experienced a problem whereby it appeared that Cognos was pulling down the entire active directory every time we ran a report, prior to issuing the sql to the DB.  Not sure what the issue was, as that occured on a test box we were using during our evaluation.  When we installed again after our purchase, the problem went away.
Timing is everything.

jiunshen

I took the SQL, which generated by report studio, and ran it in SQL server. It worked fun and just spent 1 or 2 sec.

We havent setup to use AD yet. It is still under developing environment. However, I have tried to turn off the virus protect sodtware (we are using McAfee) and some reports had a pretty good spead then.

Just curious, does Cognos have any document or list and give us some suggestions about the confliction with other softwares? Our server do need an AD and a virus protect software.

sir_jeroen

What you can try is increasing the sort buffer size to 16MB (you can do this in Cognos Configuration ). But watch out: Don't over do this because then you'll get errors like 'Cannot allocate memory) 16MB is a safe size that works. What this setting does is allocating more memory for actions that aren't performed on the DB side but on the C8 side. This will probably solve your problems because the sql is ready in 1-2 seconds (just as you said). Btw... are you hosting C8 on a server using HyperThreading? Then I would recommend you to disable HyperThreading. This increased performance in my situation.