Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Website performance issues caused by bad Limitations "1=1"

Website performance issues caused by bad Limitations "1=1"

Updated March 11th, 2016

Overview

This article describes website performance, which may be affected by bad limitations in the Limitations table of the database.

Environment

All NPM versions

Cause 

Bad limitations can be created in the limitations table in the database, which affects the website performance. Bad limitations happen if do not complete creating a limitation. Check the limitations table in the database for limitations where the WhereClause is 1=1.

Resolution

  1. Check the limitations table in the database for Limitations where the WhereClause is 1=1.
  2. If the limitations exist, run the following query to remove them:
    Delete from Limitations Where WhereClause = '1=1'
  3. After the limitations have been removed, stop all Orion services using the Orion Service Manager.
  4. Run the following Queries to remove the references to the limitations from the tables.
    • Delete From LimitationSnapShots
    • Delete from ContainerMemberSnapshots
  5. Restart the Orion Services using the Orion Service Manager.
     

The tables would rebuild, which should improve the Orion performance.

Last modified
15:24, 8 May 2017

Tags

Classifications

Public