FB TraceManager 3 - Documentation

Analysis - Register Analysis

Analysis - Register Analysis

Previous topic Next topic  

Analysis - Register Analysis

Previous topic Next topic  

To register/create a new analysis, select the parent node and then click the New Analysis sub-toolbar button item. This will open the Analysis Registration Wizard dialog.




Enter the following information:


1.Display name: This is the text of the node shown in the tree view
2.Analysis name: A logical name of the analysis, which might get used in some way (e.g. when integrating the analysis results with the reporting engine) in later versions of FB TraceManager 3
3.SQL: Define the underlaying SQL query. Either by hand or by using the Visual Query Builder. Inspect the result set by clicking the Execute Query button
4.Cube filename: Path to a physical cube file in the file system. A cube file includes data and the cube definition of a previously saved analysis. If a cube file is provided, data of the cube and not the result set of the SQL query is used for analysis tasks and vice versa. If the filename does not include path information, then FB TraceManager 3\Analysis is used as directory behind the scene. If the file does not exist, then this will simply ignored upon opening the analysis
5.Schema filename: Path to a physical schema file in the file system. In difference to a cube file, a schema file only includes information about dimensions, hierarchies etc. but no data. The same rules in respect to path information and non-existing file as for the Cube filename applies


Click Next to get to the dialog to enter an optional description.


Click Finish to finalize the registration process.



What's next: Once an analysis object is registered, you are ready to open the cube and apply OLAP/pivot-like ad-hoc queries on the underlaying data. This will be discussed with a step-by-step example in the next section Walk Through Analysis Example.


See also

Analysis Basics

Analysis Walk Through Analysis Example

Analysis Reuse Possibilities

Analysis Data Source



Event Processing