• Does not look like it is settings related.

    Here is the code executed via each client tool:

    SET QUOTED_IDENTIFIER OFF

    SET ARITHABORT OFF

    SET ANSI_NULL_DFLT_ON OFF

    SET ANSI_DEFAULTS OFF

    SET ANSI_WARNINGS OFF

    SET ANSI_PADDING OFF

    SET ANSI_NULLS OFF

    SET CONCAT_NULL_YIELDS_NULL OFF

    SELECT S.quoted_identifier,

    S.arithabort,

    S.ansi_null_dflt_on,

    S.ansi_defaults,

    S.ansi_warnings,

    S.ansi_padding,

    S.ansi_nulls,

    S.concat_null_yields_null

    FROM sys.dm_exec_sessions S

    WHERE session_id = @@SPID;

    DECLARE @a sql_variant

    SET @a = ROUND(0.5,0);

    SELECT CAST(SQL_VARIANT_PROPERTY ( @a , 'BaseType') AS varchar(10)) [BaseType]

    ,CAST(SQL_VARIANT_PROPERTY ( @a , 'Precision') AS varchar(10)) AS [Precision]

    ,CAST(SQL_VARIANT_PROPERTY ( @a , 'Scale') AS varchar(10)) AS [Scale]

    ,CAST(@a as varbinary) Binary

    SELECT @a

    SSMS:

    quoted_identifier arithabort ansi_null_dflt_on ansi_defaults ansi_warnings ansi_padding ansi_nulls concat_null_yields_null

    ----------------- ---------- ----------------- ------------- ------------- ------------ ---------- -----------------------

    0 0 0 0 0 0 0 0

    BaseType Precision Scale Binary

    ---------- ---------- ---------- --------------------------------------------------------------

    numeric 1 1 0x010100010A000000

    -------------------------------------------------------------------------------------

    An error occurred while executing batch. Error message is: Arithmetic Overflow.

    SQLCMD:

    quoted_identifier arithabort ansi_null_dflt_on ansi_defaults ansi_warnings ansi_padding ansi_nulls concat_null_yields_null

    ----------------- ---------- ----------------- ------------- ------------- ------------ ---------- -----------------------

    0 0 0 0 0 0 0 0

    BaseType Precision Scale Binary

    ---------- ---------- ---------- --------------------------------

    numeric 1 1 0x010100010A000000

    ------------------------------------------------------------------------------------------

    .0

    The error message as such also indicates a client error as SQL Server errors usually look a little different, for example like this:

    Msg 8115, Level 16, State 8, Line 2

    Arithmetic overflow error converting numeric to data type numeric.

    Best Regards,

    Chris Büttner