MSSXEDEADLCK SAP (Deadlock Information for MSSQL Server from X-Events) Structure details
Description: Deadlock Information for MSSQL Server from X-Events
Structure field list including key, data, relationships and ABAP select examples
MSSXEDEADLCK 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 "Deadlock Information for MSSQL Server from X-Events" 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_MSSXEDEADLCK TYPE MSSXEDEADLCK.
The MSSXEDEADLCK table consists of various fields, each holding specific information or linking keys about Deadlock Information for MSSQL Server from X-Events data available in SAP. These include TM (Time when deadlock occurred), PROCESSID (Deadlock process ID), VICTIM (Was this process a victim), SPID (MS SQL Server process ID).. 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 MSSXEDEADLCK 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 |
| DT | Date when a deadlock occurred | MSSDLDT | DATS | 8 | DATUM | ||||
| TM | Time when deadlock occurred | MSSDLTM | TIMS | 6 | SYTIME | ||||
| PROCESSID | Deadlock process ID | MSSDLPID | CHAR | 32 | |||||
| VICTIM | Was this process a victim | MSSDLVICTIM | CHAR | 1 | BOOLEAN | ||||
| SPID | MS SQL Server process ID | MSSSPID | INT2 | 5 | INT2 | ||||
| DB | Database name | MSSDB | CHAR | 128 | MSSSYSNAME | ||||
| WAITRESOURCE | Wait Resource as seen in sysprocesses | MSSWAITRSC | CHAR | 40 | |||||
| WAITTIME | Process wait time | MSSDLWAITTM | DEC | 20 | |||||
| HOSTNAME | Application server name | MSSAPPHOST | CHAR | 20 | MSHOST | ||||
| HOSTPID | MS SQL-Server host process id (= OS work process ID) | MSSHOSTPID | CHAR | 8 | WPPID | ||||
| LOGINNAME | Login name | MSSLOGINNAME | CHAR | 128 | MSSSYSNAME | ||||
| INPUTBUF | Output from DBCC INPUTBUFFER for lock display | MSSINPUTBUFF | CHAR | 40 | |||||
| TXACTNAME | Transaction name | MSSTXACT | CHAR | 64 | |||||
| OWNEROBJNAME | Owner object name | MSSOWNOBJ | CHAR | 512 | |||||
| OWNERINDNAME | Owner index name | MSSOWNIND | CHAR | 512 | |||||
| OWNERMODE | Owner mode | MSSOWNMODE | CHAR | 20 | |||||
| WAITEROBJNAME | Waiter object name | MSSWAITEROBJ | CHAR | 512 | |||||
| WAITERINDNAME | Waiter index name | MSSWAITERIND | CHAR | 512 | |||||
| WAITERMODE | Waiter mode | MSSWAITERMODE | CHAR | 20 | |||||
| DEADLOCKGRAPH | Deadlock graph | MSSDLGRAPH | STRG | 0 | STRING | ||||
| SQLHANDLE | handle pointing to sql statment or procedure | MSSSQLHANDLE | CHAR | 130 | MSSHANDLE | ||||
| STMT_START_OFFSET | Start statement offset | MSSSTARTOFFSET | INT4 | 10 | INT4 | ||||
| STMT_END_OFFSET | Statement end offset | MSSENDOFFSET | INT4 | 10 | INT4 |
| Key field | Non-key field |
How do I retrieve data from SAP structure MSSXEDEADLCK using ABAP code?
As MSSXEDEADLCK 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 MSSXEDEADLCK as there is no data to select.How to access SAP table MSSXEDEADLCK
Within an ECC or HANA version of SAP you can also view further information about MSSXEDEADLCK 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