...
Similar to standard SAP functionality, with in the OutBoard browser, it is now possible to view the number of entries.
Filter (F5)
| Info | ||
|---|---|---|
| ||
Filter |
...
Object types in OutBoard Browser Filter
Export Data to Microsoft Excel (F9)
| Info | ||
|---|---|---|
| ||
In OutBoard Browser it is possible to Export data to Microsoft Excel |
...
To view the data, just open the .XML document in chosen destination folder.
PSAs and Change Logs
For proper management of temporary data (such as PSAs and ChangeLogs), Datavard developed housekeeping solution: ERNA.
...
The PSA DAP is kept. By selecting "Delete DAP" the DAP can be deleted. By selecting "Display Details", the details of the selected object can be seen. For viewing the Logs for the selected object the "Display Logs" must be selected. The compression ratio can be recalculated by selecting "Calculate compression ratio" or calling report /DVD/NLS_CALC_CONV_RATIO.
Field selection for Index
| Info | ||
|---|---|---|
| ||
The field selection functionality allows you to select fields according to which the indexes in the storage table will be created. Searching on selected fields will be faster however archiving will be slower. |
...
When new data is added to NLS archive of an InfoProvider, the Indexes will be updated and used.
Parallel rebuild of Outboard for Analytics indexes
| Info | ||
|---|---|---|
| ||
Parallel rebuild of indexes is available. Now the user may define number of parallel tasks that will be running for Index rebuild, as well as time restrictions. |
...
Relevant settings for OutBoard Indexes rebuild:
INDEX_PAR_BUILD – number of parallel tasks that can be running at the same time
Secondary indexes
Before speaking about Secondary indexes it is important to remind the logic for reading NLS data. Upon archiving, the SELECTs on archived DSOs need to be adjusted in order to read the archived data. In this case the SELECT formula reading archived DSO needs to be rewritten using NLS lookup API method (refer to the documentation part for NLS lookup).
...
After the Secondary index is defined; you can check the performance improvement during the access to NLS data. NLS Secondary indexes usage needs to be allowed beforehand via the OutBoard Settings and the needed Secondary indexes have to be built.
As of OutBoard for Analytics SP21 release, Secondary indexes are available for OutBoard without Storage Management, too.
Storage for Secondary indexes
Standard OutBoard index can be stored only in primary database. In comparison to the OutBoard Secondary index, which can also be stored in external (transparent) database as a transparent table. In the OutBoard settings, the first step is to define the storage that is going to be used for storing the secondary index tables:
...
When the storage is defined, it can be used when the Secondary index is created. In current release only external databases of type DB2 and ORACLE are supported. For an Oracle database the most suitable transparent storage should have the connection mode M (massive insert into external Oracle database):
Secondary indexes
The secondary indexes can be created from OutBoard Browser -> right click on archived InfoProvider. If not available, contact Datavard consultancy to allow this functionality in your environment (parameter INDEX_SEC_ALLOWED):
...
| Inactive: The SI will not be used in NLS readings(also even if allowed), in order to be activated again, the report /DVD/NLS_INDEX_SEC_REFRESH has to be run for DSO/index |
| Active: The SI will be used in NLS readings(if allowed) |
| Running: The rebuild of SI is running at the moment (SI will not be used in NLS readings, even if allowed) |
| Disabled: The rebuild of SI was not successful, there isn’t any other way to active the SI as rebuild it completely (in OTB Browser or via report: /DVD/NLS_INDEX_SEC_REBUILD) |
Usage of secondary index
| Tip |
|---|
It is recommended to define OutBoard secondary index on objects that restrict the data the most during the access. Usually indexes defined on objects such as doc_number or deliv_number or on fields in filters with fixed values (e.g. comp_code = '0012') are the most suitable. |
The usage of secondary indexes can also slow down the performance in cases where the NLS data is read heavily and not filtered at all. For this scenario, the usage of SI can be turned off on different levels (read below).
OutBoard Settings for Secondary Index
INDEX_SEC_ALLOWED
- enables SI functionality in OTB browser, and is not editable via OTB settings (this parameter will be probably removed in next OutBoard SP)
...
- used to define block factor parameter for ORACLE hints for SELECTs used in logic for secondary index rebuild – the higher the number, the better performance. However, if set to a very high number, the FAE condition will be rewritten to a range condition, which can slow down the performance (to be checked with person responsible for maintaining parameters in TA RZ11, which values is the most suitable).
Optional usage of Secondary index
Let us discuss this topic on one example scenario. Having an end-routine of transformation it may happen, that there are multiple lookups on same DSO with very small differences. The same lookup on archived data using different filtering (e.g. EQ conditions vs. NE conditions in filter) may result in different performance impact. Secondary Index logic could improve the performance for some of the lookups, but for others the usage of this logic can have a negative impact on the lookup performance.
In this case the enhanced logic for choosing the Secondary Index can be used. The lookup is then identified:
...
INDEX_SEC_SEARCH_REGEX
the string used to find the row with the HASH ID. E.g. if using an export parameter of a class method, enter here the name of the export parameter.
Default: Empty. In this case only string "INCLUDE" is used when scanning the code.
Aggregates
| Info | ||
|---|---|---|
| ||
In an aggregate the dataset of an object (InfoCube, DSO) archived by OutBoard is saved redundantly and persistently in a consolidated and summarized form into the database. Using OutBoard Aggregates, it is possible to access the archived data very quickly in reporting. |
...
Items in an OutBoard Aggregate
Aggregate logs
For entering the Logs menu, right-click on the aggregate and select "View logs" or mark the aggregate and click on the Logs icon.
...
To display a specific log, double-click on the log. The log information can be seen below in the Message section.
OutBoard Aggregate Logs
OutBoard Aggregate Settings (for Star schema aggregates)
There are multiple OutBoard parameters, which can be adjusted in order to tune the performance when creating and reading OutBoard star schema aggregates:
...