SQL Server: datediff function resulted in an overflow when using MILLISECOND

A bit later response but may help.
In SQL 2016 MS introduced function DATEDIFF_BIG which will (according to type size) overflow in difference bigger than something like 290k years. But technet article have same time difference as basic DATEDIFF – https://msdn.microsoft.com/en-us/library/mt628058.aspx