2 Replies Latest reply on Jan 11, 2019 10:04 AM by bourlis

    Orphaned Limitations clarificaiton

    bourlis

      I just ran a Orion Deployment Health Check and one of the items that came back was to check for orphaned limitations.  It supplied a list of found orphaned limitations and then a KB article to resolve it.  The KB article is MT103094 and here's the URL for it  https://support.solarwinds.com/Success_Center/Orion_Platform/Knowledgebase_Articles/Troubleshoot_orphaned_limitations_in_Orion_Platform_products.

       

      I just need to 100% understand the SQL script before I do anything. 

       

      The KB says to run the following query ...

       

      "DELETE FROM [Limitations] WHERE [LimitationID] NOT IN

      (select [LimitationID1] as LimitationID from [Accounts] where [LimitationID1] is not null union

      select [LimitationID2] as LimitationID from [Accounts] where [LimitationID2] is not null union

      select [LimitationID3] as LimitationID from [Accounts] where [LimitationID3] is not null union

      select [LimitationID] as LimitationID from [Views] where [LimitationID] is not null)"

       

      So here's my question, do I enter this SQL query as is or do I need to fill in the limiationIDs that are bad???

       

      Case in point here's one of the orphaned limitation errors "Found orphaned Limitations: Limit the Account based on the Custom Property 'Region' in the 'NodesCustomProperties' table (id: 3)"

       

      Do I need to enter limitationID 3 anywhere in this script or does this script remove the bad entry for limitationID 3?