Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > SQL filter is not working in Resources when using NodeId

SQL filter is not working in Resources when using NodeId

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,675 Votes: 0 Revisions: 7

The database structure has changed in NPM v11.5. When using custom SQL filters working with Nodes table, the references to the NodeId should be updated to NodesData.NodeId.
NodesData.NodeId<10 is ok.
NodeId<10, it will stop working for NPM v11.5 and other Core 2015.1 products.

Applies to: NPM v11.5 and Core 2015.1 products 

Last modified

Tags

Classifications

Public