>I'm assuming you have rows in there "during the day" of Sept 17, maybe with times of 3 pm, ETC.
>
>the thing to remember is that when you use '20130917' on a datetime column, there's an implied midnight. So your original query will only capture those rows that occurred on 9/17 at midnight...not ones that happened throughout the day.
>
>You can try any of these...
>
>
>
select * from mytable where date_time >= '20130917' and date_time < '20130918'
>
>or
>
>
select * from mytable where cast(date_time as date) = '20130917'
>
>Though the first is likely to perform better than the 2nd....
Just a follow up question, please. I like the second solution (using Cast) better because it eliminates need for Time consideration. Do I understand correctly that the performance hit is on the server where SQL Server has to Cast (convert) each row's value from DateTime to Date? If so, how much of an impact you think it will have on a table, say, of about 100,000 rows? Seconds? Minutes?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
