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

MDX

Started by Vick, 22 Apr 2008 05:47:26 PM

Previous topic - Next topic

Vick

Can anybody tell me what does mdx stands for and how it can be used in reportstudio ?

Also I would like to know what would be the advantage of using pass-thru sql in Cognos 8.

Thanks,
Vick.

rockytopmark

#1
Umm...  did an internet search, and low and behold there is information out there!!!

http://search.yahoo.com/search;_ylt=AiCgyJIS4fFayDqfHORXtBZ82PAI?p=mdx+language&fr=my-myy&toggle=1&cop=&ei=UTF-8

"Multidimensional Expression"

Cognos 8 will create the necessary MDX behind the scenes.

Suraj

Framework Manager generates the most optimized SQL possible, while preserving its functionality. In this way, Cognos SQL offers the most added value.

Native SQL is the SQL the data source uses, such as Oracle SQL. You cannot use Native SQL in a model query subject that references more than one data source in the project.

Pass-through SQL lets you use Native SQL without any of the restrictions the data source imposes on sub queries. Pass-Through SQL query subjects are not processed as subqueries. Instead, the SQL for each query subject is sent directly to the data source where the query results are generated.

blom0344

Quote from: Suraj Neupane on 23 Apr 2008 12:35:57 PM
Framework Manager generates the most optimized SQL possible, while preserving its functionality. In this way, Cognos SQL offers the most added value.


" most optimized SQL possible"

Yes, theoretically, but we have  seen pretty messed up stuff Cognos generates. Let's say, it tries very hard :)

"most added value"

Again in theory, the true advantage is that by using only Cognos SQL (no native expressions/functions) a framework can be used with different RDBMS (Oracle , SQL server etc) The UDA on the server will translate the Cognos SQL to the native syntax to be used in the database. Again, this is not perfect , but I think Cognos has got this pretty much under control.