Q377. what is the meaning of aggregation and rollup aggregation?

Difference between layout calculation and query calculation?

How do you hide the rows that have null values?
why we use Query Studio? what is the use of Query Studio compared to Report Studio?

Layout calculations are used to get the runtime information into the report for eg: date, no of pages etc.

Query Calculations are used to perform required logic used in the report for eg: calculation for the revenue, sums
etc.

Using Query Studio we create simple and adhoc reports where as using Report Studio we create complex and
business reports.

(b) aggregation is the grouping of data roll-up is the extension of aggregate caluse.

Query calculation is used for calculated data items and layout calculation is used for run-time information. we
can supress null values by dataformat. Query Studio is used for simple,ad-hoc reports.

a To hide the rows, which have null values use the Zero suppresion for rows.

(d) Aggregation : How query data aggregates data item at lowest level of detail.
Rollup : Specifies how query data aggregates group value for data item.

Q374. How do we create row level security in Cognos8?

(a) Using frame work manager by creating a parameter map.

(b) Row level securities can be applied by introducing filters in the query subjects in the framework manager
model.

Q370. What is render variable?

(a) When u want to hide the column based on some condition then we will go to the render variable option.

(b) Render variable is something like hiding(rendering) anything using a variable(Condition)

(c) As far as I know: Render variales are generally created to conditionally render a particular page or chart or list
or block etc.

Though the purpose of the render variable is to hide the particular item..we can't say that it is use to hide a
particular item.

Consider a scenario..
You have created two list reports for two countries

List1 is for both country1 and country2

List2 is for country 2 alone

List1 is created from the query1

List2 is created from the query2

Now u create a conditional string variable called 'Country' which uses country name as a parameter

Now u associate Variable 'Country' as render variable for List1 and List2

Now whenever u run the report..when u select country1 then automatically the two queries will be rendered to the
two list and the two lists will be displayed.

But when u select Country2 as parameter then only Query2 will be rendered and the list2 will be displayed in
Cognos viewer window.
Note: When u use Conditional variable u r just hiding the output from the user..but in the backend the two queries
will be processed by Cognos....hence ur precious time will be wasted..

But when u r using the render variable only the Queries which satisfies the parameter will be rendered and hence
the other queries will not be processed in backend by Cognos.

(d) Render Variable: - Specify a variable based on which object can be conditionally rendered.

Example for Render Variable:--

if the case is like you want to see the particular page in HTML or PDF or CSV format then

1)Create 3 pages in your report

2)every page conatins some specific data
3)name these pages as HTML PDF CSV
4)create a String vaiable with 3 values as HTML PDF and CSV
5)now in string variable put expression as .....

case
when ReportOutput() 'HTML' then 'HTML'
when ReportOutput() 'PDF' then 'PDF'
when ReportOutput() 'CSV' then 'CSV'
end

6)now go the page named HTML and select page object

7)in properties pane click on Render Variable select that string variable
8)check only HTML check box value for HTML page
9)repeat step No. 6 to step No.8 for remaining 2 pages.

now run the report :-)

Q381. Can anyone give the example for slicing and dicing of data ?(with simple query)

(a) Example:consider a product example car and the ways received orders.
product name order method
maruthi telephone booking
alto telephone booking
Mercedez telephone booking
maruthi fax booking
maruthi agent
.....

so when you do sliciing and dicing if you want to display all the products sold through internet it will display all
product sold by internet booking.ie viewing the data in different prespectives. we basically use this concept while
dealing with cubes.

(b) Slicing is a vertical view of a report and dicing is a horizontal view of a report. simple.

Q382. How to hide the prompts

1) Drag the conditional block from toolbox.

2) Place the prompt inside the conditional block.
3) Select the prompt ,properties pane set visible as no.
4) In work area prompt will not be visible now.
But when u run the report u can see the prompt.

(b) Select the prompt, in properties pane set visible as NO

Q391. In an existing Framework model, how will you add a new column to the existing table?
You can add any combination of objects to a query subject, such as query items, other query subjects, or
dimensions. You can add stand-alone calculations and filters, and you can also embed calculations and filters in the
query subject.
Steps
1. Select the query subject that you want to add items to.
2. From the Actions menu, click Edit Definition.
3. To add items to a data source query subject, click the SQL tab, and from the Available database objects box,
drag objects to the SQL box.
You can also insert a data source reference, insert a macro, embed a calculation, and embed a filter.
4. To view the system tables from the data source, select the Show System Objects check box.
5. To add items to a model query subject, click the Query Subject Definition tab, and from the Available Model
Objects box, drag objects to the Query Items and Calculations box.
You can also embed a filter.
You can change the order of items and calculations for a model query subject. However, if the query subject
contains a query item folder, you can change the order only in the Project Viewer.
6. If you want to test the query subject, click the Test tab.
7. If you want to view the SQL, click the Query Information tab.
8. Click OK.
If any modifications invalidated relationships, other query subjects, calculations, or filters, a warning appears.
Usage and aggregation property values are regenerated to reflect the changes that you made.
9. Ensure that the Usage and Regular Aggregate properties are set how you want them.

(b) First the new column shud reflect at the database side.after that if we just say Update query subject then the
new column is automatically reflected in the physical layer.

Q392. Report Studio has two SQL tabs one native SQL and another one Cognos SQL which one is get
more preference? Which one we need to consider?

Cognos SQL is most preferable because it can fetch the data from multiple databases.

(b) Cognos SQL because it improved performance of query by converting simple SQL to optimum Cognos SQL.

(c) Cognos SQL and Native SQL are two different types of SQL generated by Cognos tool. Native SQL is sub set or
same as Cognos SQL.
Native SQL contains only the functionality that got executed at database end, apart from this Cognos SQL will have
the Locally processed logic as well.

Q409. How u provide security to reports??how u provide security to packages ?

For framework manager packages, before you head away with creating a new package it asks whether or not you
want to have security set up for the package in use. Even if you haven't defined any security at this stage, you can
always goto the actions >> package >> Edit package settings and there you can define the security settings for
the package.

For reports, you can either give report-level or folder-level security by going to the properties of that and choosing
suitable roles/user groups that are supposed to be entitled to view/modify/create reports.

Q410. WHAT SHOULD BE DONE WHEN A REPORT RUNNING TIME WILL TAKE LONG TIME IN CONGNOS?

Deselect the option auto-aggregate & summary option if it selected it takes much time to get the data

(b) Go through the generated SQL and try to compare it with the regular SQL code by running the SQL in the
navigator. that will give you an estimate of the time difference.

Secondly try to check the joins. Avoid outer joins as far as possible.

thirdly try to add prompts and filters if possible to reduce the number of records to be pulled into the query.

Q412. How can we improve performance of the reports?

TO improve the performence of the report move all the calculations and filters from report level to the frame work
manager.

1. Check the Governor Settings.

2. Dont use the Not in function in the query.
3. Check the client/server balancing.
4. Avoid using complex calculations
5. Check the table qualifying and weighting.

(b) By using simple case statements and minimising the complex calculations and applying the frequently used
filter conditions at the framework level instead of applying them in the report level we can improve the
performance. By implementing distributed configuration we can improve the performance.

Q414. What is parameter maps & Session parameter?

Parameter maps: We are using Parameters Maps to secure data within our environment, so based on who runs
the report, they will only see data specific to their group within the Parameter Map they are assigned to. We'd like
to try and display this information in the footer of the reports if possible.

Session parameters: Session parameters are macros available in either Framework Manager or in Report Studio
that can be used to dynamically determine and display information about a user's session. This can be especially
handy for general display purposes (such as a person's name) or for security implementation.

Q415. What is the importance of Dimension in the Cognos?

Without Dimension and Fact cannot make a relations between tables it could not be use for joins and retrive the
data as a form of reports in Cognos.

Dimension is a major subject area through which we can analyze our business.

Q416. What is Report item

Report item is nothing but an query item when it is drag and dropped into the work area.

Example in Go sales and retailers package-> Product (is a query subject) and-> Product line is( a query item)-
>when PL is dropped into the work area then its a report item.

Q417. What is Cardinality

Cardinality specifies the nature of relationships between the query subjects. It is numeric notation.
The first type says about the type of join ie.,inner or outer join and second one says about the number of records.

(b) Carnality and join are 2 diff things ,u can see in ur Cognos application u will be having 1:n the first part
explains u about the join and the second part tells u the cardinality ,if in ur 1st part its 1:1 then equi ,if 1:0 then
outer if 0:1 then outer if 0:0 its full outer, and the second part tell u the cardinality remember cardinality never
change the query output ,it only identify the fact and dimension which is very important ,u remember if u have
muti-star schema then it should write two query depend on two fact, so pls do it correctly,
1:n represents fact
1.1 represents dim
Check where is ur measure, put many in that cardinality.

Q418. What r the filters in FWM and Report Studio

Framework manager filters are the

Standalone filters
Embedded filters

Report Studio filters are

Detail filters
Summary filters
Slicers (this is a type of filter for a particular intersection)

Q419. What is query subject

A query subject is the basic building block in Framework Manager. A query subject is a set of query items that have
an inherent relationship.

(b) Query subject can't be precisely said as a table. It is a select clause where we can pull all the columns or a set
of needed columns from the database.

For Eg: Most of the developers will be said by the Clients that they might not need some of the columns, so
obviously we developer's may ignore those columns, so a table without a single column missing can't be called as a
table, but a select statement used to get the client preferred columns.

an example query: select * from <tablename>; (a full table)

select emp_key,emp_id,emp_name from

<tablename> ( selective columns from the table, SO THIS IS THE QUERY SUBJECT)

Q423. What is difference between drill through and drill down?

Drill through means navigating from one report to a different report in order to get detailed data. while drill
up/down is done within the same report.

Drill through can be done in relational, DMR and OLAP data.

Relational to relational
DMR to DMR or relational
OLAP to OLAP, DMR or relational

Drill down/up can be done only on DMR and OLAP

Q424. What is architecture of Cognos 8

Cognos 8 is having multi tier architecture

There are three tier

1) Web Server Tier
2) Application Tier
3) Data Tier

Q426. What is the difference between list report and crosstab report?

List report show data in rows and columns versus a crosstab report show data in grids with dimension in rows and
columns and measures in cells or in the intersection points.

(b) List Report and Crosstab report both contains rows and columns but difference is list report is a detail report for
analysis whereas crosstab report is the intersection of data or summarized data for analysis.

(c) The main difference is

List report is detailed report, later we can group the rows or columns according to the requirements.

Crosstab report is already grouped data in that we can't group any row or column.

(d) Both list and crosstab displays the data in rows and columns.
List gives detailed information.
In Crosstab report the values at the intersection of rows and cols provides summarized information.

Q433. What is the difference between group and association?

In Cognos 'group' is used to suppress the duplicate values..and 'associate' is used to suppress the values if it is
one-to-one relationship.

(b) Both Group& Association eliminate duplicates in a column. But we cannot use Association alone. It should have
one to one relationship with grouped column.
Using Association is a performance enhancement technique.

(c) When we group data, Cognos sorts the data item as we grouped and removes duplicate values. We can
organize our report by grouping on one or more data items.

By associating a grouped data item to another data item we can eliminate duplicate information from our report.
We can associate one or more data items with a grouped data item.

An association is a group of users joined together for a purpose. Both group & Association eliminates duplicates
value but we cannot use association alone. An associated data items should have a one-to-one relationship with
the grouped data item.

For example Order No. is a grouped data item. For each order number there is an Order Date. Order No. and Order
Date have a one-to-one relationship.

Q446. How to test reports in Cognos?

We can test the reports in 3 ways.

Identify the static errors -> click validate button in the Report Studio
Identify the runtime errors->by executing the report
Validate the data by writing own SQL statements in the backend.

Q447. How to create users and permissions in Cognos?

This is regarding Cognos 8 to create users open Access manager -Administration from Tools of Cognos.
First create Root User Class and then create Users in the User folder and associate that user with ur Root User
Class.
After creating Users in Access Manager-Administration go to Portal page in that select Tools at the right most side
and then Select Directory in that u can specify Permission for selected users or user Classes. (Need to check)

(b) In content manager--we have one component called Cognos process manager. using process manager we can
integrate with third party tools like LDAP or NTLM. We cannot create users in ReportNet directly.in real time we can
use LDAP. (Need to check)

Q454. A list box contains 1000 records, while running the list, inside the header the content has to
scroll down. Note the header should not go up?

Go to structure menu then click headers & footers and click permanent header check box.

Q455. What is the difference between macros and prompt?

Macro is set of instructions to run report.

Prompt is just like a dialog box which will ask user to select/enter the information what he needs.

Q456. What is an associated query?

The data item linked to the group data item. The associated data item suppress the duplicate values but do not
generate a control break. It displays the only one value of associated column.

Q472. What is alias what is shortcut what is alias shortcut and diff among them if u know explain
clearly

If u perform any operation in alias it will not affect on the original data.

If u perform any operation in shortcut it will affect on the original data.

(b) The above Ans is correct, alias is also a shortcut, but with different name, uses to avoid loops shortcut is
pointer to original data.

Q473. How to find the rank in Report Studio? i need steps for this question.

1. Select the list

2. Drag the query items into the list.
3. Drag query calculation into list.
4. Name it as 'rank'
5. Develop the expression as.
6. In functions we have rank function(in summaries)
7. Drag the rank function like rank(query item)
8. If query item is number then it will give the ranks to that number.

Q479. How to improve performance in Report Studio level

Set processing property to limited local and local cache to yes at query level in RS.

Q480. What is session parameter? What is use?

In Framework manager there are two types of session parameter

1) Environment session parameter
2) Model session parameter

Environment session parameter is set when we login to FM or Cognos Connection i.e. with LDAP User.

Information like default user name, run locale etc is maintained in the session parameter. Mostly this session
parameter is used in macros along with parameter map to use session values in the query subject, model or report.

Q481. What is reprompt?

If u want to select multi items and we dont need finish button we use reprompt button.
In Cascading Prompt we have two things -:
1.) Single Select Auto Submit.
2.) Multi Select and Reprompt Button.

Q482. It is possible without same Queries (both Reports) we can build the drill trough between them?
and how?

Two Queries in two different reports can be different, but there needs to be a common link b/w two queries based
on which we can create a drill through (by passing Data Item, Parameter).

Q483. Differences between Cognos SQL & Native SQL? What are their Advantages and Disadvantages?

Cognos SQL: It Can be Excuted on any of the database.it can understand anyDB.
Native SQL: SQL Depends on Ds(oracle,SQLserver) performancewise Cognos SQL is best.it means Cognos SQL
brings only the required columns.

(b) Cognos SQL: This SQL is genreated by Cognos on the behaf of your query. It is good for your own calculation
and for the
performance tunning also.

Native SQL: This is SQL based query which has typical database format and funcatons. All the caculation done at
database only.

Q500. Why do we use determinant? Please explain with examples?

Determinants are used by the query engine to understand how to aggregate multi-grain facts linking to a single
conformed dimension. For example, you might have sales revenue in one fact, which joins to the time dimension
at the date level, and monthly sales targets in another fact, which joins to the same time dimension at the month
level. If you created a report containing (say) Month, Revenue and Target, the query engine would need to
aggregate the measures differently - revenue would need to be aggregated, but target not aggregated in this
instance. Determinants on the time dimension (in this case) allow the query engine to understand these
differences and to perform appropriate aggregation.
Q501. What is Late Arrive dimensions? Please explain with examples?

Late Arriving Dimensions? If so, these are changes to a dimension table in a data warehouse which are being
processed out of sequence (ie not changes to the current dimensional row). Dimension tables often preserve
history using Type 2 SCD behaviour, where when (for example) a product gets renamed, a new dimensional row is
added for the product, marked as the current row and allocated an Effective Date, and the existing row for the
product is marked as old and given an End Date. To preserve uniqueness, surrogate keys are often used in the
table, and these are in turn used in fact tables as the basis for the Dimension > Fact relationships. A Late Arriving
Dimension gives all sorts of headaches in this situation, because it effectively means the current history trail in the
dimension is incorrect - there are missing changes. To fix things, the missing rows need to be inserted in their
appropriate positions in the history trail, the Effective/End dates of the rows currently in the table need to be
modified to suit, then all the fact tables need to be rebuilt from scratch to regenerate the correct surrogates to link
them to the relevant rows in the dimension.