>Dragan, I think you'll find this is a date convert to human readable string issue, depending on SQL Server defaults.
>
>No doubt you also considered a parameterized query that avoids string cast and gets cached for efficiency:
>
>

ltStart={^2015-01-01}
>ltend=dtot({^2016-01-01})-1
>
>select * from mytable where mydate between ?ltStart and ?ltEnd

That's what I routinely do... just had this weird idea that, since there are no date literals in TSQL - it uses strings for that - then it may treat a date as a string at least while parsing. And as Cetin pointed out, it actually does, it's just that the default format isn't american standard.