MSD_DYSERV SAP (contains performance measures since sqlserver's last start) Structure details
Description: contains performance measures since sqlserver's last start
Structure field list including key, data, relationships and ABAP select examples
MSD_DYSERV is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "contains performance measures since sqlserver's last start" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_MSD_DYSERV TYPE MSD_DYSERV.
The MSD_DYSERV table consists of various fields, each holding specific information or linking keys about contains performance measures since sqlserver's last start data available in SAP. These include CPUBUSY (Number of seconds the cpus have been busy.), CPUIDLE (Number of seconds sqlservr has been idle), IOBUSY (Number of seconds io busy on sqlserver tasks), PCTCPU (Percent of time the cpus have been busy).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Not classified
SAP MSD_DYSERV structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| SQLUPTIME | Number of seconds sqlserver has been running | 0 | |||||||
| CPUBUSY | Number of seconds the cpus have been busy. | 0 | |||||||
| CPUIDLE | Number of seconds sqlservr has been idle | 0 | |||||||
| IOBUSY | Number of seconds io busy on sqlserver tasks | 0 | |||||||
| PCTCPU | Percent of time the cpus have been busy | 0 | |||||||
| PCTIDLE | Percent of time cpus have been idle | 0 | |||||||
| PCTIO | Percent of time io busy on sqlserver tasks | 0 | |||||||
| PACKRECD | Number of input packets received | 0 | |||||||
| PACKSENT | Number of packets sent on the network by SQL Server | 0 | |||||||
| CONNECTS | Number of attempted connections | 0 | |||||||
| PACKERRORS | Number of packets in error since sqlserver started | 0 | |||||||
| TOTALREAD | Number of disk reads done by SQL Server | 0 | |||||||
| TOTALWRITE | Number of disk writes sqlserver has performed | 0 | |||||||
| TOTALERROR | Number of disk read/write errors since sqlserver was started | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure MSD_DYSERV using ABAP code?
As MSD_DYSERV is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on MSD_DYSERV as there is no data to select.How to access SAP table MSD_DYSERV
Within an ECC or HANA version of SAP you can also view further information about MSD_DYSERV and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects