Assume that you run the sp_describe_undeclared_parameters stored procedure in Microsoft SQL Server 2014 or SQL Server 2012. When the undeclared parameter targets a decimal column, and it is calculated with an integer, the stored procedure returns an incorrect result that considers the parameter as an integer.
Note The stored procedure is called internally by the ODBC driver when you call the ODBC function SQLDescribeParam.
The issue was first fixed in the following cumulative updates of SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:
To work around this issue, change the type of the decimal column to numeric type or add ".0" to the end of the integer constant in the expression.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.