Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Having trouble figuring out a where clause with a nested or

I tired the below query which SWQL stuidio say is valid but it return a result with a DisplayName that includes "prt".

SELECT NodeId as id, DisplayName as NodeName, Status as NodeStatus FROM Orion.Nodes where (status = 2 and DisplayName not LIKE '%-PC-%') OR (status = 2 and not DisplayName not LIKE '%-PRT-%')

Same result with

SELECT NodeId as id, DisplayName as NodeName, Status as NodeStatus FROM Orion.Nodes where ((status = 2 and DisplayName not LIKE '%-PC-%') OR (status = 2 and not DisplayName not LIKE '%-PRT-%'))I assumed I need to start with the AND and nest the OR inside it, but that is not working :-)

What is the proper syntax to nest OR's in this fasion.

I don't want any result including "-PC-" or "-PRT-" in this query.

Probably a newbie question but searching I could not fins the answer.

Thanks in Advance

Find more posts tagged with

Accepted answers

KMSigma.SWI

Does this query give you the answers you want?

SELECT NodeId as Id
     , DisplayName as NodeName
     , Status as NodeStatus
FROM Orion.Nodes
WHERE Status = 2
  AND (
         ( DisplayName NOT LIKE '%-PC-%') AND
         ( DisplayName NOT LIKE '%-PRT-%')
      )

All comments

KMSigma.SWI

Does this query give you the answers you want?

SELECT NodeId as Id
     , DisplayName as NodeName
     , Status as NodeStatus
FROM Orion.Nodes
WHERE Status = 2
  AND (
         ( DisplayName NOT LIKE '%-PC-%') AND
         ( DisplayName NOT LIKE '%-PRT-%')
      )

TedKazNJ

Works perfectly, thanks a bunch, newbie error on my part.

KMSigma.SWI

Boolean logic is JUST close enough to plain English to cause problems. It happens to the best of us. And that means it happens to me all the time because I'm nowhere close to being the best.