1. The document outlines tasks for a Cognos resource to understand existing reports and code, improve performance, and reconcile reports with source data.
2. Key tasks include understanding business logic, identifying related reports, dashboards, cubes and their data sources, documenting calculations, and resolving issues by updating code.
3. The resource should have knowledge of Cognos administration, SQL, SSIS framework, and data modeling concepts to fully comprehend report logic and configurations.
1. The document outlines tasks for a Cognos resource to understand existing reports and code, improve performance, and reconcile reports with source data.
2. Key tasks include understanding business logic, identifying related reports, dashboards, cubes and their data sources, documenting calculations, and resolving issues by updating code.
3. The resource should have knowledge of Cognos administration, SQL, SSIS framework, and data modeling concepts to fully comprehend report logic and configurations.
1. The document outlines tasks for a Cognos resource to understand existing reports and code, improve performance, and reconcile reports with source data.
2. Key tasks include understanding business logic, identifying related reports, dashboards, cubes and their data sources, documenting calculations, and resolving issues by updating code.
3. The resource should have knowledge of Cognos administration, SQL, SSIS framework, and data modeling concepts to fully comprehend report logic and configurations.
1. Team need to understand about the Business logic /Calculation in FWM
2. Need to understand the "how many FWM is in place" and "how many reports" are associated with those FWM. 3. Once FWM and Reports has been identified then its easy to identified about the related Dashboard/Scorecard . Need to open the Dashboard and check that how many reports has been used in those Dashboards. 4. If client is using "Scorecard" (Standard way ), then i believe that person should have good knowledge about the "Matrix Studio" in Cognos 5. Open the Cube (in Analysis Studio) and identified that which cube has been associated with which particular FWM Package. Honestly, Documentation part can be carried over step by step when resource actually involve in project
1. To Understand the Reverse Engineering stuff person need to understand the
"Fact" , "Dimensions" and "Measures" in DWH. 2. Once FACT/Dimensions/Measures has been identified then understand the business logic behind this. 3. According to business logic then identified the "Pain area"/Issue and then resolve those defects/bugs 4. Document the business calculation and related "Query Subject" so that it will easy to understand about the populated data in Reports/Cube/Dashboards.
1. Identify the report those having problem (like performance/wrong calculation
etc.) 2. Correct the code at FWM level (in Query Subject) or in SQL stuff (in Report Studio) 3. Develop the new Cognos report as per this new calculation or newly created FWM.
1.Performance of Report cannot be only dependent upon the code of report(SQL
Queries) & FW Model but also it depends on Cognos Server tuning like Dispatcher setting, Report Server setting , Batch job setting , number of users (in peak business hours) setting etc. To configure and maintain all these it’s good if a person should have Cognos Admin knowledge too
1. Identify the report those having problem (wrong calculation etc.)
2. Correct the code at FWM level (in Query Subject) or in SQL stuff (in Report Studio) Cognos Resource has to understand the Framework of SSIS and its code. Simply copy paste of SQL code from SSIS (or its related package) cannot be helpful for a long run. So I believe that Cognos person should have good understanding of SSIS Framework too .So that he/she can replicate the same business rules (or say Transformer) into Cognos native code
Knight's Microsoft Business Intelligence 24-Hour Trainer: Leveraging Microsoft SQL Server Integration, Analysis, and Reporting Services with Excel and SharePoint