SMMSS_ALERTS - Message class for MSSQL rz20 messages
The following messages are stored in message class SMMSS_ALERTS: Message class for MSSQL rz20 messages.
It is part of development package STUN_MSS in software component BC-DB-MSS. This development package consists of objects that can be grouped under "Package for new SQL Server monitoring objects".
It is part of development package STUN_MSS in software component BC-DB-MSS. This development package consists of objects that can be grouped under "Package for new SQL Server monitoring objects".
Message Nr ▲ | Message Text |
|---|---|
| 000 | SQL Server Monitoring Object. Please check F1 help 1 level below |
| 002 | &1: function call &2 failed with exception &3. Affected MTE: &4. |
| 003 | This alert shows if level 17 or higher errors are in the SQL Server logs |
| 004 | No Severity 17 or higher messages exist |
| 005 | &1 errors exist in an error log |
| 006 | |
| 007 | This alert shows if the last good backup is too old |
| 008 | This database was last backed up successfully &1 days ago |
| 010 | SQL Server using &1% of CPU |
| 011 | This alert tracks the percentage of CPU used by SQL Server |
| 012 | &1 disk read/write error(s) have occurred |
| 013 | This alert shows the # of disk read/write errors noticed by SQL Server |
| 014 | &1 network packet error(s) have occurred |
| 015 | This alert shows the # of network packet errors noticed by SQL Server |
| 016 | This alert shows a configuration required in SQL Server has not been done |
| 017 | This alert shows which trace flags were used to start SQL Server |
| 018 | This alert shows if the memory setting for SQL Server follows SAP rec. |
| 019 | SQL Server self monitoring |
| 020 | This alert show information about the Operating System |
| 021 | This alert tracks the data cache hit ratio of SQL Server |
| 022 | This alert tracks the procedure cache hit ratio of SQL Server |
| 023 | Data cache hit ratio of &1% could be improved |
| 024 | Procedure cache hit ratio of &1% could be improved |
| 025 | This alert shows information about SQL Server build numbers |
| 026 | &1 | &2 | Chip:&3 |
| 027 | &1&2 |
| 028 | &1 | Cluster:&2| AWE:&3 |
| 029 | Memory is &1 - follows SAP recommendation |
| 030 | Memory is set to FIXED and no R/3 work processes are present on DB server |
| 031 | Memory is set to &1 and &2 dialog R/3 work procs are present on DB server |
| 032 | This alert shows how many non-R/3 connections are on the SAP DB |
| 033 | This alert shows how many connections the R/3 work procs have to the DB |
| 034 | &1 R/3 connections to the DB |
| 035 | &1 non-R/3 connections to the R/3 DB |
| 036 | This alert tracks the maximum runtime of a SQL statement |
| 037 | Single SQL statement runtime of &1ms is very high |
| 038 | This alert shows whether statistics collection is on or not |
| 039 | This alert shows if a backup is currently being run against a database |
| 040 | DB &1 is currently being backed up |
| 041 | Statistics collection is &1 |
| 042 | Last Reset: &1 |
| 043 | This alert shows when the slow SQL statement statistics were last reset |
| 044 | A backup is not currently running |
| 046 | This alert shows if disk performance statistics are on for the DB server |
| 047 | NOT on DB server - no Perfmon disk stats available |
| 048 | Yes use Detail Analysis/Disk button of trx ST06 |
| 049 | This alert shows the time since the last transaction log backup |
| 050 | Transaction log backup &1 minutes ago |
| 052 | This alert shows the count of the given object type missing from the DB |
| 053 | There are &1 &2 defined in the data dictionary and missing from the DB |
| 054 | This alert shows the percent of free space left in a file |
| 055 | This alert shows if autogrowth has been set for the DB file |
| 056 | The current size, used size, and growth setting of a DB file |
| 057 | This alert shows the MB left on the device the DB file resides upon |
| 058 | Autogrowth is &1 |
| 059 | Size:&1 Used:&2 Growth:&3 |
| 060 | &1 MB free disk space on device |
| 061 | This alert tracks the maximum runtime of a SQL statement |
| 062 | Single SQL statement run and fetch time of &1ms is very high |
| 063 | Transaction AL02 is not supported in Sql Server |
| 064 | This alert shows the ms/access |
| 065 | The ave. number of millisecs/access for this file is &1 |
| 066 | Transaction Log &1% used |
| 068 | This alert shows the % of total time used by a single statement |
| 069 | This alert shows the % of logical reads used by a single statement |
| 070 | This alert shows the % of cpu time used by a single statement |
| 071 | &1% of elapsed time caused by one statement |
| 072 | &1% of logical reads caused by one statement |
| 073 | &1% of cpu time caused by one statement |
| 074 | &1% free space in file |
| 078 | This alert shows the current kBytes/sec read for the DB |
| 079 | &1 kB/sec read for DB |
| 080 | This alert shows the batches/second processed by SQLServer |
| 081 | &1 Batches/sec processed by SQLServer |
| 082 | This alert shows the ms/write for the SQLServer LOG |
| 083 | &1 ms/wrt for the SQLServer log |
| 084 | This alert shows the seconds blocked of the oldest blocked spid |
| 085 | &1 seconds blocked |
| 086 | This alert shows the seconds of the oldest open transaction |
| 087 | &1 seconds open for a transaction |
| 088 | This alert tracks the page life expectancy reported by SQL Server |
| 089 | Page life expectancy of &1 could be improved |
| 090 | This alert shows the name of the object which caused high cpu % |
| 091 | This alert shows the object causing high logical reads |
| 200 | Data Collection |
| 201 | Check of the SQL Server Agent service status |
| 202 | SQL Server Agent service status |
| 203 | Start the SQL Server Agent service |
| 204 | Check of the last DBCC CHECKDB run |
| 205 | Last DBCC CheckDB status |
| 206 | Check the consistency of the database |
| 207 | Check of the Page Level locking setting for certain tables |
| 208 | Page level locking status |
| 209 | Run sap_z_set_parameters in MSSPROCS or use the Quick Repair button |