The places I'd look:
1) driver version
2) localization differences
3) permission differences
4) error treatment differences
if this is a large data set ---- use in-db. If you want to fix this problem --- use the filter or convert to string. If your core question isn't about the data and is about why is the query behaving x way locally vs y way on server --- 1 post the query. 2--- look at the listing of the 3 features above. For your initial question ---- convert it to string or filter out those dates in your query. That will fix your error on Server.
I'd recommend seeing if that value is being pulled when you run on Designer. Do you get an error message? There are situations where errors are ignored when running locally but fatal when running on Server --- but there are questions like --- do you want to understand Alteryx internals or do you want to fix this issue? assuming it's the later --- follow my advice. if it's the former --- turn on logging at the odbc level (in odbc 64 --- not in alteryx) on your server and see what's being passed in. compare vs your desktop.
