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 > Modifying the limitations of copy view affects the original view

Modifying the limitations of copy view affects the original view

Created by Malik Haider, last modified by Brian.Jarchow on Feb 06, 2018

Views: 301 Votes: 0 Revisions: 7

Overview

Modifying the limitations of copy view affects the original view.

Environment

NPM 11.5 and later, including NPM 12.2

Resolution

  1. Copy the original view.
  2. Edit and remove all limitations from the copy view.
  3. Re-add the limitation for the copy view.

 

Alternatively, you can create a new view as only one view was effected. 

 

Caution

Do not use this in NPM 12.2. When tested in this environment, removing the limitation from the copy view also removed it from the original view. The only known workaround at this time is to identify the view ID of the copied view and run the following query: UPDATE Views SET LimitationID = 0 WHERE ViewID = 

 

Last modified

Tags

Classifications

Public