Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > NPM 12 bug: Custom SQL filter is incorrectly formatted

NPM 12 bug: Custom SQL filter is incorrectly formatted

Created by Kevin Twomey, last modified by MindTouch on Jun 23, 2016

Views: 2,006 Votes: 3 Revisions: 3

Overview

Custom Resources are are not working when adding in filters after upgrading to NPM v12.0. The following error appears:
Custom SQL filter is incorrectly formatted.

Environment

NPM v12.0

Cause 

  • This is a bug in NPM 12.0.
  • NPM v12 has issues with FILTER in lowercase and sometimes cannot use NODES.
  • Need to use NODESDATA or NODESCUSTOMPROPERTIES instead where applicable.

Resolution

Workaround:

Edit from lowercase and also edit to a a new table structure where applicable.

Nodes.City = London'  (does not work)

NODECUSTOMPROPERTIES.CITY = 'London' (working)
 

Long Term solution:

  • This issue is verified as fixed in NPM 12.1.

  • Filter works correctly for top resources (like Top XX Volumes by Disk Space Used; Top 10 Interfaces by Percent Utilization; Top XX Nodes by Current Response Time etc) via lowercase\capital letters.

 

Last modified

Tags

Classifications

Public
/*]]>*/