Summary
This document describes the current capabilities to monitor a Microsoft SQL Server database within a
Solution Manager 7.1 system and shows examples of how to modify the standard delivered SAP template to
create alerts on other metrics associated with a SQL Server database.
Author:
Dale Adams
Company:
SAP SE
Author Bio
Dale Adams is a Senior Developer at SAP SE, and has been working since 1998 at the Microsoft Platforms
team. He is based in Redmond Washington USA.
Table of Contents
Overview ............................................................................................................................................................. 3
Default SQL Server Monitor ............................................................................................................................ 3
Customizing or Removing Portions of the Delivered Monitor ......................................................................... 5
Creating New Metrics ...................................................................................................................................... 5
Customized Use of a Single Message from SAP SQL Setup ...................................................................................... 5
Customized use of ABAP function MSS_COLL_LIST .................................................................................................. 6
Customized Use of Output From a Stored Procedure .................................................................................................. 7
Overview
This document describes the current capabilities to monitor a Microsoft SQL Server database within a
Solution Manager 7.1 system and shows examples of how to modify the standard delivered SAP template to
create alerts on other metrics associated with a SQL Server database.
6. Database Performance also contains metrics for the performance on the storage system as
measured through SQL Server. For more information, see SAP Note 987961.
For more information on the latest changes and the required fixes for the SQL Server monitor, see SAP Note
2006729.
Condition to Check
Locked pages in memory
Trace flag status
SQL Agent running
Read committed snapshots
Snapshot isolation state
SAP SQL Agent job steps failures
Last SAP CCMS Check Database appears to be clean
Auto create statistics, update statistics
SQL Server Memory optimized table exists
To create a metric checking only one of these conditions, copy the standard template and define a new
metric with the following input values used. Most of the following settings are used for the metric Buffer
Cache Hit Ratio so that metric can be copied as a baseline. Most parameters are copied also, except
MSS_CNTR_NAME and MSS_OBJ_NAME. The PATH parameter is left blank and an = is used in the
parameter value column.
Value
RFC (pull)
MSS Database Alerts Generic
Once a day or whatever
Parameter Name
MSS_OBJ_NAME
MSS_CNTR_NAME
PATH
RDI_DDIC_FIELD
RDI_DDIC_STRUCTURE
RDI_TIME_RANGE
DBCNAME
DBMC_ID
Value
sap_mon_sqlsetup
Number 1-9 from table above
=
NONE
NONE
CURRENT
$DBCNAME$
$DBMS_ID$
As an example, if your requirement is to have an alert whenever a job step failed for a job name SAP_*, you
need to create a new metric as shown above with the MSS_CNTR_NAME set to sap_mon_sqlsetup and
the MSS_OBJ_NAME set to 6. Then you can configure an email or other notification for that single alert.
The most recent version of the MSSPROCS item sap_mon_sqlsetup is required for this type of custom
metric to work. This version is in 702 Basis Support Package 17.
Value
I/O counters (Overview)
HADR_SYNC_COMMIT [ms] / request
SLOPE
I/O counters (Overview)| HADR_SYNC_COMMIT [ms] / request
NONE
NONE
CURRENT
$DBCNAME$
$DBMS_ID$
MSS_CNTR_NAME
CXPACKET [ms] / request
WRITELOG [ms] / request
@@CPU_BUSY
Purpose
Monitor parallelism
Monitor performance of transaction log
Monitor cpu utilization. Note that this metric is
based on sys.dm_os_sys_info data, not
@@cpu_busy
Value
sap_rz20_opentrx
block
sap_rz20_opentrx|block
NONE
NONE
CURRENT
$DBCNAME$
$DBMS_ID$
Related Content
SAP Note 1609057 - Server Setup Check Overview and Explanation
SAP Note 44449 - Backup strategies with the SQL server
SAP Note 1238993 - Data File Management for SQL Server
SAP Note 987961 - FAQ: SQL Server I/O performance
SAP Note 2006729 - E2E alerting for SQL Server
SAP Note 2089683 - Can't change standard SQL Server template to exclude file
SAP Note 2054273 Required changes to class CL_MSS_ALERTING_EXTRACTOR to process BTCH
providers or single setup messages from the SQL Server template
Copyright
2015 SAP SE SE or an SAP SE affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain proprietary software components
of other software vendors. National product specifications may vary.
These materials are provided by SAP SE and its affiliated companies (SAP SE Group) for informational
purposes only, without representation or warranty of any kind, and SAP SE Group shall not be liable for
errors or omissions with respect to the materials. The only warranties for SAP SE Group products and
services are those that are set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP SE and other SAP SE products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE in Germany and other countries.
Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.