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

Analysis/Query/Report Express Studio - Scope and use

Started by bloggerman, 23 Jun 2010 01:46:23 PM

Previous topic - Next topic

bloggerman

We have a requirement for ad hoc reporting/analyses. We have a dimensional package.

Could someone help me identify the right tool for it, Query Studio, Analysis Studio, Report Express.

As far as i know all 3 can be used with dimensional packages. All would allow users to drag and drop at will. So i was not sure what requirement would distinguish between the 3. Thanks for the help.

MFGF

Query studio is for ad-hoc reporting - usually where the author has a clear idea of what the report should show and how it should look.

Analysis Studio is for ad-hoc analysis - usually where the author has no clear idea of a finished report, but instead wants to browse through the data, slicing and dicing different dimensions at will  - looking for apparent trends or high/low spots and then drilling down to investigate, or doing best/worst comparisons.

Report Studio Express mode is specifically for financial-type reporting (such as a P&L report).

Regards,

MF.
Meep!

bloggerman

My understanding of the word slicing and dicing is where a user can drag and drop any dimension at will into the analysis window. Is that correct?

And, its different from the concept of slicer or Context filter where we can cut/reduce the amount of data in the measures.

If the above is true then we can drag and drop columns at will even in Query Studio. So, what puzzled me was how would Analysis studio be better for it. Is it because analysis studio is better built and gives better performance for it.

Thanks

bloggerman


MFGF

Quote from: bloggerman on 25 Jun 2010 04:23:27 AM
My understanding of the word slicing and dicing is where a user can drag and drop any dimension at will into the analysis window. Is that correct?

And, its different from the concept of slicer or Context filter where we can cut/reduce the amount of data in the measures.

If the above is true then we can drag and drop columns at will even in Query Studio. So, what puzzled me was how would Analysis studio be better for it. Is it because analysis studio is better built and gives better performance for it.

Thanks

Sorry - I missed this somehow.

When I use the term 'slicing and dicing' I am describing the process of replacing one dimension/level/set of members (in either rows or columns) with another dimension/level/set of members to provide an alternative slant to the current analysis, while simultaneously retaining any filters achieved by previously drilling down on a member.

Query Studio is really not geared up for this process - you would need to first delete a level, then drag in a new level.  Additionally, Query Studio is not member-aware - only a structural view of the data (hierarchies and levels) can be used.  Analysis Studio also has options like 'expand', 'down a level' and stacking dimensions, and features like top/bottom filtering etc.

In a nutshell, Query studio is designed for building fixed reports, Analysis Studio is designed for interactive analysis.

MF.
Meep!

bloggerman

Thanks MFGF.

Is slicing different from dicing? I was once asked abt the difference between the two. Didnt really know what it meant let alone the difference. But, now i wonder.

Would you say Report Express is more apt for creation of dimensional reports instead of query studio?

MFGF

Slicing and dicing is really referring to the fact that there are multiple dimensions in your crosstab (in rows and columns).  Think about chopping vegatables - slicing is cutting in one plane, dicing is cutting in the opposite plane.  In Analysis, slicing and dicing is simply referring to the process of changing the rows and columns to gain new insights into your data.

Report Studio Express Mode can only use dimensional data (like Analysis Studio), but it's not an Analysis environment - it is designed explicitly to allow users to create Financial-style reports.  It's not designed for list-style reports or charts or for use with Relational packages, so it's in no way a replacement for Query Studio

Regards,

MF.
Meep!


bloggerman

Can't believe i have another question on the same topic.

What if i have a need to do ad hoc reporting requirement against dimensional data? Should i use query studio? But, would i have the option to use memebrs in query studio.

MFGF

Quote from: bloggerman on 06 Jul 2010 02:18:20 PMCan't believe i have another question on the same topic.

That's what we're here for!  :)

Quote from: bloggerman on 06 Jul 2010 02:18:20 PMWhat if i have a need to do ad hoc reporting requirement against dimensional data? Should i use query studio?

Yes, provided you don't need to work with individual members or sets.  If you want to do level-based reporting, Query Studio is ideal.

Quote from: bloggerman on 06 Jul 2010 02:18:20 PMBut, would i have the option to use memebrs in query studio.

Not directly - only a structural view of the package (hierarchies, levels and attributes) is available in Query Studio.  If you need to use a member-based view of the data to build the report, you would need to use Report Studio.

Regards,

MF.
Meep!