I pulled together some tests which reproduce the behavior I'm encountering. I've been testing using java build 1.8.0_101-b13, mssql-jdbc driver version 6.1.0.jre8 and Microsoft SQL Server 2016 (RTM) - 13.0.1601.5 (X64).

I suspect the issue might be caused by the driver code incorrectly assuming that the precision and scale values of BigDecimal mirror those of the decimal data type in SQL Server, namely the code found here.

Let me know if any additional details would be helpful.