L'exemple suivant illustre un cas courant d'analyse d'écarts d'une mesure dans
le temps, traité via des formules MDX dans un cube Microsoft Analysis
Services.
Cela pourrait s'appliquer à un "reporting" sur la qualité des prévisions de
vente par rapport aux ventes réalisé.
Tag - Business Intelligence
mardi 23 mars 2010
Analyse d'écarts dans le temps avec Analysis Services
Par jb le mardi 23 mars 2010, 16:47 - Décisionnel
vendredi 13 novembre 2009
Cognos 8 Macro functions list
Par jb le vendredi 13 novembre 2009, 11:24 - Décisionnel
We have seen that cognos macro functions available in framework manager are also available in report studio.
Here is a simple list of existing Cognos Macro with description.
mardi 10 novembre 2009
Last period prompt option in Cognos report Studio
Par jb le mardi 10 novembre 2009, 20:42 - Décisionnel
When you build a new report with some prompts, including a time dimension; you may want to add an option to automatically select the last Period. this way users can :
- see their last data without chosing it in a time tree (but with ability to choose another one).
- schedule a report witch will always select the last period available.
This can be done by using a set containing the #promptmany()# Cognos macro
lundi 9 novembre 2009
SSAS Batch Processing with XMLA
Par jb le lundi 9 novembre 2009, 12:10 - Décisionnel
When you want to schedule the processing of SSAS database (using Sql Server jobs), you have two options :
- create ans SSIS package containing Analysis services tasks & schedule it.
- Build ans XMLA script & schedule it.
Here we will see how you can build an XML script describing the processing tasks you want to execute.
mercredi 26 août 2009
setup cognos to work with OLAP MSAS cubes security
Par jb le mercredi 26 août 2009, 20:38 - Décisionnel
Usually, when we create a data source in Cognos, it is easier to specify a connection using Cognos Service Credentials. This means that all connections to the data source are done using the Cognos service user's profile.
- Advantage of this method is that it needs less setup on the corresponding database server (only one account).
- Disadvantage is that you cannot make use of "row level security" as all Cognos users will connect using the same profile (Data source has no information about current Cognos user).
To take advantage of an eventual user level security setup behind Cognos data sources, we need to connect using the current Cognos user's profile.
Row Level security in MSAS
Par jb le mercredi 26 août 2009, 07:11 - Décisionnel
Security implementation in Analysis Services
In some cases, companies want to give different level of access to strategic data, depending on user’s profiles. Analysis services gives us ability to secure cubes data by building Roles containing security rules, mainly by filtering dimensions data.For example, if you have a cube giving Turnover amounts per salesperson, salesmen should see only the data corresponding to their sales area only. Also, one manager may want to see data for all areas he’s responsible for.
This document describes how we can achieve security on the sales Area axis for the sales domain. Notice taht in this example, we are using Cognos as reporting tool. This addidional layer has no impact on the way we setup MSAS & Active directory, results will be the same with Microsoft Reporting services