SELECT whatever
   FROM yourtable
  WHERE somedatecol >= '20080721'
    AND somedatecol <  '20080722'

quote:

---

Originally posted by tfountain

In that case, using the BETWEEN keyword will be of value as well. But honestly, if the underlying data is small and you can guarantee it will remain that way then it's a wash IMO.

---

quote:

---

Originally posted by Michael Valentine Jones

quote:

---

Originally posted by tfountain

In that case, using the BETWEEN keyword will be of value as well. But honestly, if the underlying data is small and you can guarantee it will remain that way then it's a wash IMO.

---

I don't see any reason to use something that is bad in a lot of cases when the solution Jeff posted is the best way to do things.




CODO ERGO SUM

---

quote:

---

Originally posted by tfountain

quote:

---

Originally posted by Michael Valentine Jones

quote:

---

Originally posted by tfountain

In that case, using the BETWEEN keyword will be of value as well. But honestly, if the underlying data is small and you can guarantee it will remain that way then it's a wash IMO.

---

I don't see any reason to use something that is bad in a lot of cases when the solution Jeff posted is the best way to do things.




CODO ERGO SUM

---

I didn't say Jeff was wrong either. I was simply suggesting that using the BETWEEN operator would work as well - the assumption was with Jeff's example and that was not implicitly stated. Instead of doing the comparision using the equality operators. That's all.

My second statement holds true and it's not 'bad' by any means. How it's used can be bad. There's a difference. I do realize the prior statements are true as well in terms of not being able to use an index in a WHERE clause - but again, review my prior posts regarding using it wisely. The point here being what's worse - a table scan on a small table when querying normally or not using an index on a small table when using some sort of function around the left side of the condition. It's a wash unless you really care about the extremely small marginal gain there might be.

---

where dateadd(dd,datediff(dd,0,datecol),0) = '20080721'
where datediff(dd,'20080721',datecol) = 0
where datecol between '20080721' and '20080721 23:59:59.997'

where datecol >= '20080721' and datecol < '20080722'

quote:

---

Originally posted by tfountain

Honestly, I'm not sure of what your argument is. For query purposes, I have this code encapsulated in a function where all I need to do is something like so:

WHERE <db>.dbo.<function>(date) = '1/1/1900'

I'll admit I use this function mainly for removing time off of variables for other uses and but on occasion I will use it in queries. If you know what you're doing and don't use this in the wrong situations, there's no argument - period.

I'll concede simply because arguing over something as trival as this is a waste time for both of us.

---

WHERE dbo.UDF_Date_function(date) = '1/1/1900'

quote:

---

Originally posted by tfountain

Honestly, I'm not sure of what your argument is. For query purposes, I have this code encapsulated in a function where all I need to do is something like so:

WHERE <db>.dbo.<function>(date) = '1/1/1900'

I'll admit I use this function mainly for removing time off of variables for other uses and but on occasion I will use it in queries. If you know what you're doing and don't use this in the wrong situations, there's no argument - period.

I'll concede simply because arguing over something as trival as this is a waste time for both of us.

---

WHERE dbo.UDF_Date_function(date) = '1/1/1900'

quote:

---

Originally posted by cbeganesh

select * from ttt
where joindate >= '01/01/2008'+' 00:00:00'
and joindate <= '01/01/2008'+' 23:59:59'

---