trboyden (6/23/2016)

---

http://www.w3schools.com/sql/sql_dates.asp

http://www.w3schools.com/sql/func_convert.asp

https://msdn.microsoft.com/en-us/library/ms187347.aspx ( ISDATE() Function)

https://technet.microsoft.com/en-us/library/ms179465(v=sql.105).aspx ( Handling Database Engine Errors )

http://sqlmag.com/t-sql/t-sql-best-practices-part-2 (See datetime best practices...

trboyden (6/23/2016)

---

Jeff Moden (6/23/2016)

---

No need for the sarcasm. You made an incorrect statement that newbies would misinterpret and I made sure they weren't mislead.

Shifting gears to the subject at...

trboyden (6/21/2016)

---

Jeff Moden (6/20/2016)

---

That's not true at all. SQL Server will take a couple dozen date/time formats...

Ken Hiatt (6/20/2016)

---

This was definitely wrong on many levels, but what strikes me is that they are expecting to extract a time from the first 8 characters of a variable...

LC

I quite agree that the table should not be using the varchar (20) field to store the date values.

What surprised me was how sql server interpreted the wrong data...

trboyden (6/20/2016)

---

It's not so much a critique of the original code which I would expect you would understand needs refactoring. However, one should expect strange outcomes when data is passed...

As expected a lot of people will be stuck on the fact that the code was wrong in the first place. That is not without question. However, the interesting thing...