MSQ_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
MSQ_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_MSQ_DYSERV TYPE MSQ_DYSERV.
The MSQ_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 CPUs have been busy (sum for all CPUs) .), CPUIDLE (Number of seconds CPUs have been idle (sum for all CPUs) .), IOBUSY (Number of seconds SQL Server tasks were busy with IO.), 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: Cannot Be Enhanced
SAP MSQ_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 SQL Server has been running. | MSQDSSQLSC | INT4 | 10 | INT4 | ||||
| CPUBUSY | Number of seconds CPUs have been busy (sum for all CPUs) . | MSQDSCPUBY | INT4 | 10 | INT4 | ||||
| CPUIDLE | Number of seconds CPUs have been idle (sum for all CPUs) . | MSQDSCPUID | INT4 | 10 | INT4 | ||||
| IOBUSY | Number of seconds SQL Server tasks were busy with IO. | MSQDSIOBSY | INT4 | 10 | INT4 | ||||
| PCTCPU | Percent of time the CPUs have been busy. | MSQDSCPPCT | INT4 | 10 | INT4 | ||||
| PCTIDLE | Percent of time CPUs have been idle. | MSQDSIDPCT | INT4 | 10 | INT4 | ||||
| PCTIO | Percent of time SQL Server tasks have beeen busy whit IO. | MSQDSIOPCT | INT4 | 10 | INT4 | ||||
| PACKRECD | Number of network packets received. | MSQDSPCKRD | INT4 | 10 | INT4 | ||||
| PACKSENT | Number of network packets sent out by SQL Server. | MSQDSPCKST | INT4 | 10 | INT4 | ||||
| CONNECTS | Number of attempted connections to SQL Server. | MSQDSCONN | INT4 | 10 | INT4 | ||||
| PACKERRORS | Number of network packets with error since SQL Server start. | MSQDSPCKER | INT4 | 10 | INT4 | ||||
| TOTALREAD | Number of disk reads done by SQL Server (physical reads). | MSQDSTOTRD | INT4 | 10 | INT4 | ||||
| TOTALWRITE | Number of physical disk writes done by SQL Server. | MSQDSTOTWR | INT4 | 10 | INT4 | ||||
| TOTALERROR | Number of disk read or write errors since SQL Server started | MSQDSTOTER | INT4 | 10 | INT4 |
| Key field | Non-key field |
How do I retrieve data from SAP structure MSQ_DYSERV using ABAP code?
As MSQ_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 MSQ_DYSERV as there is no data to select.How to access SAP table MSQ_DYSERV
Within an ECC or HANA version of SAP you can also view further information about MSQ_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