Timeline for SQL DATEDIFF coercion differences between databases on same SQL instance?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| Mar 24, 2015 at 17:57 | comment | added | Colin Dabritz | This was originally posted in on stackoverflow here: stackoverflow.com/questions/29238048/… | |
| Mar 24, 2015 at 17:45 | comment | added | Colin Dabritz | This was the answer. So in this case datediff on Compatibility mode (SQL 2005) 90 or earlier fails, as it tries to do a datediff conversion with a datetime, and the date is out the valid range. Testing on (SQL 2008) 100 or later works, probably doing a better (working) conversion internally like datetime2. Thanks so much! | |
| Mar 24, 2015 at 17:44 | vote | accept | Colin Dabritz | ||
| Mar 24, 2015 at 17:42 | history | answered | Aaron Bertrand | CC BY-SA 3.0 |