Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

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


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


All NPM versions


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.


  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.
    • Truncate table LimitationSnapShots
    • Truncate table ContainerMemberSnapshots
  5. Restart the Orion Services using the Orion Service Manager.

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

Last modified