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

cognos Message regarding Governor RQP-DEF-0542 and RQP-DEF-0543

Started by jive, 12 Mar 2010 10:22:50 AM

Previous topic - Next topic

jive

Hi ,
After reading some proven practice on Cognos site I check were the metadata was coming from for each query" Most of them come from the database, and this is supposed to be slower then from the model. How can I correct that situation.

One time we change the connection name there is a possibility it's the reason why I have that. One other time a "Content Manager Datasource" was create and add to the definition of all data source we have. can this action create that problem.

Thanks for your time and I hope my English is too bad

blom0344

I think you are mixing thinks up a little.  The Metadata is in the model, though this is 'only' used to generate a request (query) on to the database. In a number of cases the database will not be enough , like when you define running totals or define post aggregate filters. In that case part of the processing is done on the server (as a final touch to get the required results).
This is limited local processing (as opposed to database only)

jive

So when I saw a message like this one
"message severity="information"title="QE-DEF-0469 QE Message"type="general">RQP-DEF-0543 Metadata will be retrieved from the database, because a simple DB query subject definition with matching metadata does not exist"

what is the meaning of this ?

thanks for your help

blom0344

It means that Cognos needs an additional database lookup in order to compile the ultimate SQL to send. Unless you use a passthrough query the respective UDA will need to recompile the Cognos SQL to a version that can be executed on the database.

Beneficial should be:

1. Import database objects to the model WITHOUT changing the simple SQL in volved  (select * from [datasource].
)
2. Evaluate and update query subjects in the model
3.Reference model objects in model query subjects

My 2 cents: this overhead is usually dwarfed by the time it takes to render the results in the browser, so who cares..    ;D

jive

Thanks a lot for your time and your help  ... sometimes even the documentation are not really clear. Now it's make more sense to me.

Thanks again