Arithmetic overflow error converting expression to data type numeric

[armanis]

This problem only happens if I have a DECIMAL(28,15) column is set with the maximum value of 9999999999999.999999999999999 and I use the option to compare with only 3 decimal places.

Here is the message in the dialog

"An error has occurred in prosafe_7x vs prosafe_tux (localhost).dcomp.

Additional information: Cannot compare prosafe_7x.dbo.RV_basecontrol with prosafe_tux.dbo.RV_basecontrol on localhost.
Arithmetic overflow error converting expression to data type numeric.

Do you want to continue process?"

If I set it to 9999999999999 then it works.

I faced a similar issue elsewhere and that is likely to be a .NET exception because .NET will round it up and cause the overflow exception when converting from double and decimal and vice-versa.

We were about to buy a licence until we faced this issue.

Can you give us an estimate on how long it will take you guys to fix it so that we can buy a licence?

Cheers,

Sil

[alexa]

Could you please describe it in more detail and specify what you mean by "I use the option to compare with only 3 decimal places"?

Also, please provide us the versions of dbForge and SQL Server.

Additionally, a video, screenshots or scripts would be of help.

You can send a reply straight to our support system at alexaATdevartDOTcom and supportATdevartDOTcom .

[armanis]

Thanks for the quick reply.

I've sent the screenshots via email.

SQL Server 2012, 2016 and 2017

How to replicate

1) Create a table with a field of type DECIMAL(28, 15)
2) Add a row with the decimal columns set with the maximum value of 9999999999999.999999999999999
3) Try comparing 2 copies of the same DB with the option "Round float types up to 3 digits" checked
4) The error message will show up

Cheers,

Sil

[armanis]

Btw, we are interested in your product exactly for that comparison option. If it could be configured to 10 digits it would be even better.

The tool works fine with that options unchecked.

Cheers,

Sil

[alexa]

Thank you for the reply.

We were able to reproduce this issue and will fix it in one of the next product builds. We will notify you once it's available for downloading.