Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-TOO (Application Component) Workbench Tools: Editors, Painters, Modelers⤷
SWLT (Package) SQL Performance Tuning Worklist
Basic Data
| Data Element | SWLT_D_MD_UPDATE_KIND |
| Short Description | SWLT - Defines the update kind for the table meta data |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Update |
| Medium | 15 | MD Update Kind |
| Long | 20 | MD Update Kind |
| Heading | 25 | MD Update Kind |
Documentation
Definition
DB Table Meta Data (e.g. buffering type, number of columns, number of key columns, table class, ...) can be used within SWLT as additional information.
For example: If you want to analyze a select statement, it's probably relevant whether its target db table is buffered or not.
Therefore SWLT keeps database meta data for each original system (where SQLM data is from). This data is transferred to SWLT next to the main SQLM data within the SQLM snapshots.
Use
With this update option you can choose whether you want to:
- Use only meta data of tables that are not known in SWLT yet (delta)
- Use meta data of all tables (updates/overwrites existing)
- Use no meta at all
Be aware that you maybe don't want to use option "For All Tables" if you import an outdated SQLM data file.
Dependencies
Example
For example:
System A is a productive system that runs SQL Monitor. System B is a quality assurance system that runs SWLT. You transfer the SQL Monitor data from A to B using a snapshot and the meta data option "For All Tables".
Now you can see information about table buffer type etc. of affected tables when using SWLT in system B.
At a later point in time a new database table has been created within System A and you want to update the SQL Monitor data. So you create another snapshot and use the meta data option "For New Tables Only".
Now only the meta data for the newly created table will be imported.
At a later point in time you want to do a general update, maybe because situation in system A changed again, and you create another snapshot using meta data option "For All Tables".
Now the existing meta data information will be overwritten with the current information for all tables.
History
| Last changed by/on | SAP | 20141013 |
| SAP Release Created in | 740 |
