Based on testing, `WHERE NOT` is valid SQL syntax 

```
 where  not ( x = 10  y > 5 )

```

However, I don't follow that from the definition:

To me, the T-SQL definition of a search condition doesn't seem to allow producing `NOT ( <search_condition> )`" 

The spec/docs makes it seem like the only legitimate target for a unary negation is a predicate. To produce `not ( <search_condition> )` it looks like this requires the statement to be the right hand side of a conjunction or disjunction...Is the spec incorrect, or am I missing a way to produce this?

```
< search_condition > ::= 
    { [ NOT ] <predicate> | ( <search_condition> ) } 
    [ { AND | OR } [ NOT ] { <predicate> | ( <search_condition> ) } ] 
[ ,...n ] 
<predicate> ::= 
    { expression { = | < > | ! = | > | > = | ! > | < | < = | ! < } expression 
    | string_expression [ NOT ] LIKE string_expression 
  [ ESCAPE 'escape_character' ] 
    | expression [ NOT ] BETWEEN expression AND expression 
    | expression IS [ NOT ] NULL 
    | CONTAINS 
  ( { column | * } ,'< contains_search_condition >') 
    | FREETEXT ( { column | * } ,'freetext_string') 
    | expression [ NOT ] IN (subquery | expression [ ,...n ] ) 
    | expression { = | < > | ! = | > | > = | ! > | < | < = | ! < } 
  { ALL | SOME | ANY} (subquery) 
    | EXISTS (subquery)     } 

```