Question

Try the following on MSSQL 2005:

select convert(char(2), 123)

The key here is that char(2) is too small to accept the value ‘123’. I would expect to see a truncation error here, but instead the value “*” is returned.

Update:
A few of the answers showed how to cast in a way that will cause an error. That’s not really what I need. We have lots of code that uses a specific field that used to be declared char(2) but has since been changed to int. My goal here is to make sure that code that hasn’t been converted will fall over if it encounters data that it can’t handle. So we can go fix it.

Interestingly, dsolimano notes that changing the above type to nchar causes the expected error, and Justin Niessner notes that both of these are by design. Strange inconsistency given that nchar is for Unicode support, hey?

From the answers I have here, it appears that I sadly can’t make the server throw the error for existing code.

Answer 1

Microsoft’s convert/cast page seems to indicate that you can cast to nchar(2) if you want to get an error instead of * or truncation, and indeed that is what I get:

SELECT CAST(123 AS NCHAR(2))

Msg 8115, Level 16, State 2, Line 3
Arithmetic overflow error converting expression to data type nvarchar.