I was trying (by a mistake) to update bit typed field with non-bit value. It took me some time to realize the cause for not getting this field updated (non-bit value). I was supprised that no native arithmetic overflow exception was raised by the SQL Server query engine.
Does anyone know why is works that way (no exception) for "bit overflow" updates?
On the side I immediately tested updating TINYINT with out-of-range value and it raised an (expected) exception.
I used Microsoft SQL Server 2014 (SP1-CU7) (KB3162659) - 12.0.4459.0 (X64)