Versions Compared

Old Version 1

changes.mady.by.user SNP

Saved on

compared with

New Version 2

changes.mady.by.user Marian Vidra

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Busy and quiet times of queries and DTPs

The analysis provides an overview of busy and quiet times of queries and DTP loads which were executed on all InfoProviders on a monitored system. The heatmap Heatmap shows a total number of queries, DTPs or their sum. You can switch it with buttons Combined (Query & DTP), DTP or Query. Data is aggregated by weekdays and hours and it can be filtered by specific InfoProvider or by analyzed period. This analysis can help you to find quiet hours e.g., for operations which need more system resources. Also the busiest hours can be examined and their content can be split into other less busy hours.

Busy and quiet times of queries and DTP analysis chart


InfoProviders size

The analysis provides an overview of all InfoProviders in the system divided into 3 categories. Each category represents a size of InfoProviders that correspond to a particular group . E(e.g. "10%" group represent first 10% largest InfoProviders and their corresponding size). By clicking on a bar, the application will be redirected to "Top InfoProviders" analysis, where "Top %" filter will be applied accordingly.

InfoProviders size analysis chart

...

You can switch to the table view for more detailed information where data can be downloaded into a CSV file for further processing.


InfoProviders by year

This analysis provides an overview of InfoProviders in the system. Two charts are displayed here:

  • Distribution by InfoProvider type - displays the whole system per InfoProvider type
  • InfoProviders - objects in the chart are sorted by their size by default and can be further filtered

Both charts always display last 4 years + all others merged into other group (e.g., 2013 and lower) based on the amount of InfoProvider data that belong to the group.

InfoProviders by year analysis chart 


You can filter data and also switch to the a table view for more detailed information where data can be downloaded into a CSV file for further processing.

It is possible to switch color mode of the bottom chart to "Query usage". This colorizing mode groups data in InfoProvider by their respecting reporting usage. All data that were reported on less than 10 times are colorized with blue color and all data reported on more than 1000 times are colorized with red color. Warm data colorized with orange color belong to the category between these two threshold values. 

InfoProviders by query usage analysis chart


You can change these threshold values by clicking on the  button.


NLS potential

Based on the analysis performed in the system, the visualization provides you with an overview on the potentials for archiving of particular object types (such as InfoCubes, DataStore objects, Write-Optimized DSOs) in form of column charts. 

NLS potential analysis chart

...

These analyses provide information about how data is distributed in InfoProviders based on a specified characteristic and based on how many times these data areas were accessed by reporting (queries). The number of Data distribution analysis tiles depends on the settings on the central system. By default the BW analysis is delivered with only one predefined Data distribution analysis. The Data distribution analysis tile displays the number of analyzed InfoProviders which contain the specified characteristic. The figure below figure displays the temperature based data categorization which is a type of data distribution and is by default included in the package.

...

ColumnDescription
Object contains technical name of an InfoProvider
Typedisplays a type of an InfoProvider (InfoCube, DSO, aDSO, WODS)
Descriptionlong description of an InfoProvider
Size [MB]

total object size in MB

  • InfoCube: F table + E table + dimension tables
  • DSO / WODS / ADSO: new table + active table

table size calculation differs by various database types

  • HANA database: main memory + delta memory + index
  • Other databases: table size (without index)
Rowsnumber of rows in InfoProvider data tables (same tables are used as in the size calculation)
Number of queries

the total number of queries that read data in an InfoProvider

  • This column can contain a value > 0, also in the case the InfoProvider is empty. This event occurs when a query uses a MultiProvider which includes this InfoProvider
Trend - Number of queriesvisualization displaying the usage of data areas - values are rounded to natural numbers
Trend - Size [MB]visualization displaying the size of data areas - values are rounded to natural numbers
Split characteristic

describes applied time characteristic

  • if the characteristic is empty, then the Data distribution analysis doesn't identify a suitable characteristic and distribution of the size and number of queries isn't successful
Archived size [MB]

size of unpacked archived data in MB 

  • size of data in an online database that would be occupied, if all archived data would be reloaded
DTP source counthow many times an InfoProvider is used as a source in DTP load requests
Last DTP exec.timestamp of the last DTP load request execution
DTP dest. countnumber of DTP requests loaded into an InfoProvider (including reloaded requests from an archive)
DTP dest. relv

number of requests (DTPs for InfoCubes, activation requests for DSOs) relevant for straggler analysis

  • by a DSO object - request is relevant, when a Change log contains records of this request
  • by an InfoCube object - request is relevant, when request records are not compressed
  • by a WODS object - requests aren't relevant, as WODS can be archived only based on request creation date
  • by an ADSO object - based on the type of the object, the ADSO behaves the same as the equivalent object type (DSO, WODS, InfoCube)
    • as ADSO object can have various settings. In general the analysis collects requests for the following object types
      • Data warehouse - data mart
        • information is gathered from the inbound table
      • Corporate memory – reporting capabilities
        • information is gathered from the inbound table
      • Data warehouse – delta calculation
        • information is gathered from the Change log table
DTP stragglers

number of requests with straggler records (see more details)

  • subset of requests relevant for straggler analysis, which contain at least one straggler record
DTP stragg. rowsnumber of rows which represent straggler records
Number of lookups Lookups

number of lookups Lookups that are present in a the system for an InfoProvider

  • number of lookups Lookups in the source code


Data distribution analysis standard view

...

The columns number of queries and size of data areas depend on data distribution settings of a particular analysis. These columns are created based on data groups you specify in your analysis. See the chapter (DI-2005) Define the Data Distribution Analysis for details about how to define data distribution and it's its respective data groups for analysis. Each of these columns contains a sum (for sizes) and sum (for the use) of corresponding data area values. The footer of the table displays the number of records was already loaded to the table. This number will gradually increase, as you scroll down in the table.

Info

Note that data groups will be empty, if the distribution analysis could not identify the split characteristic for a particular InfoProvider and distribution wasn't performed. For more information why split characteristic was not identified please check , see the chapter (DI-2005) Define the Data Distribution Analysis.

You can filter the content of a table column by clicking on the column header. There is also a possibility to download the table content (without chart columns) into a csvCSV. file by clicking on  toolbar button. You can also hide/show specific column groups by clicking on column group in View options toolbar. You can sort results based on field of your preference, by clicking again on column header:

...