SQL NOT
Flips a condition's truth value — everything that WOULD have matched now gets excluded, and vice versa.
What & Why
NOT negates whatever condition follows it. NOT channel = 'google_ads' keeps every row where that condition is false.
See How It Works
BUSINESS QUESTION
Campaigns outside the google_ads channel.
| id | name | channel | spend | start_date | end_date | status | target_segment |
|---|---|---|---|---|---|---|---|
| 1 | Spring Launch | google_ads | 55000.00 | 2024-01-15 | 2024-03-31 | active | smb |
| 2 | Retention Webinar | 45000.00 | 2024-02-10 | 2024-04-15 | active | enterprise | |
| 3 | Finance Retargeting | 50000.00 | 2024-03-12 | 2024-05-31 | active | enterprise | |
| 4 | Enterprise Search | google_ads | 60000.00 | 2024-04-01 | 2024-06-30 | active | enterprise |
Watch not check each rowRow 1 of 4
-- checking Spring Launch: NOT google_ads = google_ads?FALSE — dropped| name | channel |
|---|---|
| Spring Launch | google_ads |
| Retention Webinar | |
| Finance Retargeting | |
| Enterprise Search | google_ads |
NOT channel = 'google_ads' is false for Spring Launch.
EXAMPLE QUERY
SELECT name FROM marketing.campaigns
WHERE NOT channel = 'google_ads';Now You Try
Practice this concept
Marketing wants campaigns that are not paused.
Available schema
marketingPrefix tables with marketing.table_name.
namestatuschannelmarketing.campaigns| Column | Type |
|---|---|
| id | integer |
| name | text |
| channel | text |
| spend | numeric |
| start_date | date |
| end_date | date |
| status | text |
| target_segment | text |
| legacy_id | text |
query.sql
Sign up free to try it on a real business scenario