How to avoid limited local processing

[Ben Rose]

Hello,

I am running C8.3 on Teradata.  Some of my Report Studio reports require me to specify limited local processing in FM.  When I use this option, I can see that the parameters are not being passed to the WHERE clause on the database SQL statements.  This in turn is causing poor performance due to the larger volume of data being passed over the network. 

Are there specific things in report studio that I can look for that are likely require limited local processing, such as certain functions, or master detail relationships?  I would like to either restructure my report so that limited local processing is not required, or ensure that parameters are being passed to the database.

My queries are only hitting one fact table at a time.

Thanks,
Ben

[TJohnson]

Have you set the processing property on the query to 'Database Only'?

[Ben Rose]

When I choose that database only processing, the report fails and delivers a message that limited local processing is required.

[blom0344]

Aggregate filters surely will invoke limited local processing as Cognos uses it's own strategy to filter a returned SQL-based set.

[mikene]

If you enclose SQL-Code in curly brackets {}, it will be delivered direct to the ODBC-driver or whatever you use to access your datasource. But, you must be precise when writing your code since it will not be tested by Cogos.