Cognos Quick Guide
On a page I have a list report which i am using for master detail relationship for two crosstab on the Once you have a page break/bursting defined Cognos by default throws a settings to run these queries in parallel as default is sequential. Cognos Quick Guide - Learn Cognos in simple and easy steps starting from basic to Connections, Packages, Framework Manager, Relationships in Metadata An Operational Database supports parallel processing of multiple transactions. 4 Architecture of InfoSphere Information Server Warehouse and Cognos 8 BI 10 BIarchitecture. 38 Framework Manager keeps control over multisource relationship settings 39 Multisource parallel model development.
Select a value and click the right pointing arrow to move the value into the selected column. You can use the Ctrl key to add multiple values at tone time.
Click OK when the filter is defined. You can go to the query explorer and view the filters. Click the insert calculation button and select the calculation to perform.
To change the order of the operands or the name of the calculated item added to the report, click Custom. The calculation appears as a new row or a column in your report.
Drilling Drill up and drill down is used to perform analysis by moving between levels of information. Drill down is used to see more detailed information to lowest level and drill up is used to compare the results.
To drill down or up in both a row and column simultaneously, click on the value at the intersection of the row and the column, and then click again. Cognos - Analysis Studio Analysis Studio is used to focus on the items that are important for the business. You can do comparisons, trend analysis and analysis like top and bottom performers and also allow you to share your analysis with others.
Analysis Studio is not only used by BI Analysts but also by business users who understand business and want to find answers to business queries using historical data. You can use Analysis Studio to compare and manipulate data to understand the relationships between data and its relative importance.
Whether you want to assess revenue growth or to identify top performers, Analysis Studio provides the filtering, calculating, and sorting support you need for analysis. Interface The Analysis Studio consists of several areas that are shown in the following areas and are explain in detail as well. You can display analysis in the form a Crosstab, chart or a combination of both. And lastly there is the Overview Area as well. Cognos - Create an Analysis To create an analysis in the Analysis studio, you have to select a package as data source.
You can create a new analysis or use an existing analysis as reference to create a new analysis by changing its name before saving it. Go to Report Studio as shown in the following screenshot. In a new dialog window, select a Blank Analysis or Default Analysis.
After selecting, click OK. The Analysis Studio starts. The items that you can use in the analysis are listed in the Insertable Objects pane. Cognos - Save an Analysis To save an analysis, you can click on the save button at the top as shown in the following screenshot.
Cognos - Open Existing Analysis To open an existing Analysis, locate the name of the analysis that you want to open and click it.
It is opened in Analysis Studio. You can make any changes as per the requirement. You can also open a new analysis while working in an existing analysis, click the new button on the toolbar.
The new analysis maintains the state of the source tree in the Insertable Objects pane and maintains any items on the Analysis Items tab. Cognos - Event Studio Cognos Event Studio is a Web-based tool that allows you to create and manage agents to monitor data and perform tasks when the data meets predefined thresholds. Events You can specify an event condition to perform a task.
An event is defined as query expression in a data package.
Cognos Relationships in Metadata Model
When a record matches the event condition, it causes an agent to perform tasks. When an agent runs, it checks the data for any event instances.
- Improving IBM Cognos Report Studio Master Detail Report Performance
- Cognos - Relationships in Metadata Model
- Creating a simple data module
This is the maximum that a system with a single CPU core would be able to run and it limits the number of reports that can be run simultaneously.
For most systems the default settings will not make effective use of the hardware resources. This can create a performance bottleneck when the server is under load. You also do not want to have so many BIBus process running that you reach a point where they require more physical RAM than what the server can provide.
The upper limit on the number of BIBus processes that Cognos will allow to run at the same time is controlled by the Max Number of Processes tuning parameter. This setting exists for both the Report Service and the Batch Report Service, and is divided into settings for peak and non-peak hours. So you have in fact 4 settings: Maximum number of processes for the batch report service during non-peak period Maximum number of processes for the batch report service during peak period Maximum number of processes for the report service during non-peak period Maximum number of processes for the report service during peak period Keep in mind that there are 2 settings for each period, so if the number of processes for the batch report service during peak period is set to 2, and the number of processes for the report service during peak period is set to 4, you could have up to 6 BIBus processes running at the same time during the peak period.
The database server performance and network performance then impact report performance. A way to test if this is an issue is to select a slow running report with a single report query and get the SQL generated for the report.Cognos Master Detail Relationship
A large difference may indicate an issue like local processing see belowbut if the times are fairly close you may want to look at ways to improve the database and network performance. Another environment change that may help is to add more dispatchers on different servers.
B - Report Design Issues 1 - Local processing When a report is run, Cognos looks at the requirements of the data container in the report, the query in the report that the data container uses and the metadata in the report package.
From that it generates a query in Cognos SQL. That query is then converted to the native SQL of the data source and sent to the database.
Sometimes there are functions used in a report that cannot be converted to native SQL and sent to the database. In that case the native SQL is formed without those elements, and after Cognos receives the results it applies the functions that could not be sent down. This has the potential of creating large performance issues.
The native SQL then will not have that filter. It could result in a much larger set of rows being returned than needed, and Cognos will have to consume much time and system resources to process this large result set down to what is actually needed for the report. An easy way to test if this is affecting a particular report is to set the Processing property on every query in the report to Database Only, then run the report.