Just a heads-up... converting dates to strings, and then comparing the strings uses a a LOT of resources, especially if enough queries are pounding your database and cycling through your cache quickly. Take advantage of your execution plan by NOT compa...

Just a heads-up... converting dates to strings, and then comparing the strings uses a a LOT of resources, especially if enough queries are pounding your database and cycling through your cache quickly. Take advantage of your execution plan by NOT compa...

Here are more good examples of why you should neve, EVER use BETWEEN when searching for date ranges... and some GOOD ALTERNATIVES with examples. http://garybhaley.com/ComparingDatesInSQL.pdf TheSQLWhisperer...

Here are more good examples of why you should neve, EVER use BETWEEN when searching for date ranges... and some GOOD ALTERNATIVES with examples. http://garybhaley.com/ComparingDatesInSQL.pdf TheSQLWhisperer...

Ok, IMHO, the problem here is the use of WHILE EXISTS. Using SET has more serious problems. You should always use SELECT whenever you can, instead of SET. If you're using SET to assign a value to a variable, and the SQL fails, the variable retains ...

Ok, IMHO, the problem here is the use of WHILE EXISTS. Using SET has more serious problems. You should always use SELECT whenever you can, instead of SET. If you're using SET to assign a value to a variable, and the SQL fails, the variable retains ...