Basis Errors and Solutions

Symptom

The AutoGrowth MTE ( CCMS_MSS_SPACE_fileag_ma ) is Red and shows the message “No free space in file”. Autogrow on but not all files can grow, is shown.
Other terms

Autogrowth, SQL Server rz20, CCMS_MSS_SPACE_filepct_ma, sap_mon_sqldbfiles, CCMS_MSS_SPACE_MGMT, Mountpoints, Mount point
Reason and Prerequisites

Changes to RZ20 for SQL Server in 2008 were done in order to make customers aware that it is NOT sufficient to solely rely on setting “autogrowth on” for managing data files. Autogrowth is a safety feature to allow file growth. To maintain acceptable performance, it is better to follow the procedure mentioned in
SAP with Microsoft SQL Server 2005 – Best Practices for High Availability, Maximum Performance, and Scalability.pdf
( February 6, 2007) specifically the paragraph
Setting autogrowth – Avoid situations where automatic growth is set by manually increasing the size of the data files proportionally in advance. Although the data files can be manually manipulated proactively, leave autogrowth on as a safety measure in case of an emergency such as when the database runs full.
However, there are development and test systems where relying on autogrowth is acceptable. This note changes the code so that the No free space in file message is still visiable in the dbacockpit->Space->Overview Files Overview tab, but doesn’t file an alert for the MTE CCMS_MSS_SPACE_fileag_ma. The MTE CCMS_MSS_SPACE_filepct_ma will still fire an alert when no free space exists, regardless of the setting of autogrowth.
If you are using rz20 to monitor a remote system, you must reinject the stored proecedure sap_mon_sqldbfiles in order to avoid the message “No free space in file” in the MTE CCMS_MSS_SPACE_fileag_ma.

Solution

Apply 7.0 SP 18.
If you need to get rid of the alerts in MTE CCMS_MSS_SPACE_fileag_ma prior to SP 18, than use note 181114 to change the stored procedure sap_mon_sqldbfiles, which is attached to this note.