| SMMSS_ALERTS080 |
This alert shows the batches/second processed by SQLServer |
| SMMSS_ALERTS081 |
&1 Batches/sec processed by SQLServer |
| SMMSS_ALERTS082 |
This alert shows the ms/write for the SQLServer LOG |
| SMMSS_ALERTS083 |
&1 ms/wrt for the SQLServer log |
| SMMSS_ALERTS084 |
This alert shows the seconds blocked of the oldest blocked spid |
| SMMSS_ALERTS085 |
&1 seconds blocked |
| SMMSS_ALERTS086 |
This alert shows the seconds of the oldest open transaction |
| SMMSS_ALERTS087 |
&1 seconds open for a transaction |
| SMMSS_ALERTS088 |
This alert tracks the page life expectancy reported by SQL Server |
| SMMSS_ALERTS089 |
Page life expectancy of &1 could be improved |
| SMMSS_ALERTS090 |
This alert shows the name of the object which caused high cpu % |
| SMMSS_ALERTS091 |
This alert shows the object causing high logical reads |
| SMMSS_ANALYZE000 |
SQL error &1: &2 &3 &4 |
| SMMSS_ANALYZE001 |
RFC Error encountered |
| SMMSS_ANALYZE002 |
Database system &1 is not supported |
| SMMSS_ANALYZE003 |
SQL Error &1 |
| SMMSS_ANALYZE004 |
Error trying to connect to &1 |
| SMMSS_ANALYZE005 |
Please select one line in the table (Single click) |
| SMMSS_ANALYZE006 |
Function is not yet available |
| SMMSS_ANALYZE007 |
Error & occured at function module MSS_COLLIST |
| SMMSS_ANALYZE008 |
& end of values reached |
| SMMSS_ANALYZE009 |
Not more than & values graphically displayed at the same time |
| SMMSS_ANALYZE010 |
DB Error occured while trying to get/change collector status |
| SMMSS_ANALYZE011 |
Authorization error when trying to get/change collector status |
| SMMSS_ANALYZE012 |
Collector Job is in an inconsistent state |
| SMMSS_ANALYZE013 |
No Explain Available |
| SMMSS_ANALYZE014 |
No stored procedure found |
| SMMSS_ANALYZE015 |
Can't get text for stored procedure |
| SMMSS_ANALYZE016 |
Line exceeds limit of &1 |
| SMMSS_ANALYZE017 |
Error when calling connection display/maintain screen |
| SMMSS_ANALYZE018 |
Job is already started |
| SMMSS_ANALYZE019 |
Job is already stopped |
| SMMSS_ANALYZE020 |
ADBC database error (&1) occurred |
| SMMSS_ANALYZE021 |
Database system &1 not supported |
| SMMSS_ANALYZE022 |
Statement can't be explained. It is too large. |
| SMMSS_ANALYZE023 |
This program is only for MS SQL Server |
| SMMSS_ANALYZE024 |
No file found |
| SMMSS_ANALYZE025 |
File error |
| SMMSS_ANALYZE026 |
Cancelled |
| SMMSS_ANALYZE027 |
Unknown file open error. |
| SMMSS_ANALYZE028 |
Processing trace file to the end |
| SMMSS_ANALYZE029 |
No objects found |
| SMMSS_ANALYZE030 |
No indexes found |
| SMMSS_ANALYZE031 |
SQL text not found |
| SMMSS_ANALYZE032 |
Wrong input |
| SMMSS_ANALYZE033 |
Table not found |
| SMMSS_ANALYZE034 |
No server list |
| SMMSS_ANALYZE035 |
SQL error &1: &2&3&4 |
| SMMSS_ANALYZE036 |
WMI data is not available. Check xp_cmdshell permissions |
| SMMSS_ANALYZE038 |
Statement is not blocked. No plan available in cache |
| SMMSS_ANALYZE046 |
Error occurred during file selection |
| SMMSS_ANALYZE047 |
Error occurred during download |
| SMMSS_ANALYZE048 |
&1 bytes transferred |
| SMMSS_ANALYZE049 |
Can't construct path for target file |
| SMMSS_ANALYZE050 |
File copy failed: &1 |
| SMMSS_ANALYZE051 |
Can't copy file to application server home directory: &1 |
| SMMSS_ANALYZE052 |
This function is only available on a CI running on the DB Server |
| SMMSS_ANALYZE053 |
Database connection error |
| SMMSS_ANALYZE054 |
No collector data for selected date/time range |
| SMMSS_ANALYZE055 |
Select columns,press the graph toolbar button with an open graph window |
| SMMSS_DBACCESS000 |
SQL error &1 occured: &2&3&4 |
| SMMSS_DBACCESS001 |
Invalid input |
| SMMSS_DBACCESS002 |
Command unsupported |
| SMMSS_DBACCESS003 |
No data |
| SMMSS_DBACCESS004 |
Index not found |
| SMMSS_DBACCESS005 |
Multiple indexes found |
| SMMSS_DBACCESS006 |
No schema found |
| SMMSS_DBACCESS007 |
No indexes found |
| SMMSS_DBACCESS008 |
Table not found |
| SMMSS_DBACCESS009 |
Internal error |
| SMMSS_DBACCESS010 |
Table or stored procedure must be provided |
| SMMSS_DBACCESS011 |
Invalid input string |
| SMMSS_DBACCESS012 |
Invalid object |
| SMMSS_DBACCESS013 |
Wrong database release |
| SMMSS_DBACCESS014 |
Not running on SQL Server |
| SMMSS_DBACCESS015 |
Database not found |
| SMMSS_DBACCESS016 |
No database access |
| SMMSS_DBACCESS017 |
Time two less than time one |
| SMMSS_DBACCESS018 |
Server data one is wrong |
| SMMSS_DBACCESS019 |
Server data two is wrong |
| SMMSS_DBACCESS020 |
Lock type is invalid |
| SMMSS_DBACCESS021 |
Invalid exclusion status |
| SMMSS_DBACCESS022 |
Invalid inclusion status |
| SMMSS_DBACCESS023 |
Invalid SAP spids |
| SMMSS_DBACCESS024 |
Invalid resource locks |
| SMMSS_DBACCESS025 |
Number of tables greater than fixed limit |
| SMMSS_DDIC000 |
*** Memory parameters *** |
| SMMSS_DDIC001 |
A clustered index already exists: &1 |
| SMMSS_DDIC002 |
You can only set CLUSTERED for one index |
| SMMSS_DDIC003 |
There can be only one clustered index |
| SMMSS_DDIC004 |
There can be only one clustered index |
| SMMSS_DDIC005 |
There can be only one clustered index |
| SMMSS_DDIC006 |
The same file group must be chosen for the table and the clustered index |
| SMMSS_DDIC007 |
FILEGROUP is not set for the table |
| SMMSS_DDIC008 |
FILEGROUP is not set for the clustered index |
| SMMSS_DDIC009 |
FILEGROUP is not set for the table and the clustered index |
| SMMSS_DDIC010 |
FILEGROUP is not set for the table |
| SMMSS_DDIC011 |
Reserved |
| SMMSS_DDIC012 |
Reserved |
| SMMSS_DDIC013 |
Reserved |