yea Jason I figured it out by myself, it's just a logical thinking issue.
first you need to load what you do want to see with an OR
and with that selection in mind, you need to eliminate the things you don't want to see with AND's.
otherwise you don't get the right results.
This works, but increases loading time heavily.
WHERE ([Business segment]='DOWNSTREAM' OR [Business segment]='UPSTREAM')
AND [Business unit] <> 'TRADE' AND[Business unit] <> 'OTHER DOWNSTREAM'
AND[Business unit] <> 'PHOSPHATES' AND [Business unit] <> 'SPECIALITY JVS');
maybe it would be better to load everything at once, and then make the selections you need from the resident table and drop the source table.
If it wasn't for the new field you are creating (Date) you could use Exists() instead of WHERE and retain an optimized load. Might be best to do this anyway - you can test what's faster:
1. Load the above using Exists(), with the Date
2. Load the above using Exists(), without the Date, then joining the Date afterwards.
Let me know if you need help with the script from here.