SLA Filter using != in the Push Fields qualification causes performance issues

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Service Level Management


    BMC Service Level Management



    There is a != qualifier in the Push Fields qualification of the SLM:Measurement:ReqUpdateLastSVTMeasFlag`! filter that results in a full table scan of the SLM:Measurement form data table:

         ('SVTInstanceID' = $SVTInstanceID$) AND ('InstanceId' != $InstanceId$) AND ('LastSVTMeasurement' = "Yes") AND ($Request ID$ != 'Request ID')

    This full table scan has been identified as a performance issue during submit or update of an incident that attaches a service target when there are a significant number of records in the SLM:Measurement form.  The filter executes for any request based service target, which means the full table scan will have an impact on performance from any submit or update of a service desk request, an incident request or a change request which results in attach of a service target.




    Legacy ID:KA298276


    There is a design change with the 7.5 release of SLM with a change to the Push Fields qualification of this filter that will eliminate conditions that force a full table scan.  The revised Push Fields qualification is the following:

         ('SVTInstanceID' = $SVTInstanceID$) AND ('LastSVTMeasurement' = "Yes")

    This change to the Push Fields qualification of the SLM:Measurement:ReqUpdateLastSVTMeasFlag`! filter can be done manually at anytime.  This change is not considered a customization and should not be considered for overlay with upgrade to 7.6.04 or later release of ARSystem server.



    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles