SQL DATEDIFF coercion differences between databases on same SQL instance?
This will happen if you are in a lower compatibility level (80) and indirectly try to convert a value that is outside the supported range of the older types. I have added an example illustrating exactly this scenario in the following answer:


What is the actual behavior of compatibility level 80?


See the section of my answer entitled Conversions involving new date/time types.