>>In practice, I run this query for one client - another parameter- and return about a hundred rows, and the time is miniscule.
Thank you, and fair enough. Also I get the point that "good enough" becomes more acceptable when available processing cycles are cheap and scalable. I'm reminded of JVP's argument many, many years ago that SQL Server is always quicker than dbfs because if it isn't, you can get a bigger server. ;-)
>>It includes the time
In that case, check out Naomi's most recent SQL example. Looking at the end date: in your BETWEEN expression deployed to the customer, will it include an invoice at (say) 3pm on last day of month? My understanding is that SQL Server casts the time for a datetime that lacks seconds as 00:00:000, meaning that the 3pm invoice on last day of month, is excluded by this enddate expression. Hence previous observations. Maybe I'm wrong?
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
