Comparing numeric values is more complex than it may seem at first glance. The main reason for occurring difficulties is the type (format) of the numeric data fields. The equal values can be represented in different format, and this variance may cause problems during data comparison and synchronization operations. Below is the instruction on resolving the issue:
In the data options section, you can specify options for the numeric data types.
Check the Use custom scale option if you need to specify the decimal places in this data comparison operation.
Enter the number of decimal places in the Scale field (becomes active when you check the Use custom scale option) that will be involved during the current data comparison operation.
Here’s how it works: for example, in the left table we have a data row with the value of 3.14, and in the right table the value of the corresponding field is 3.14159. The following table shows the results of comparison operation, depending on usage of the custom scale.
|Custom scale setting||Comparison result||Note|
|Unchecked||Not equal||Right value has more decimal places|
|Set to 2||Equal||Right value is rounded to 3.14|
|Set to 4||Not equal||Right value is rounded to 3.1416, but still has more decimal places|
Depending on the selected database platforms used in comparison operation, the numeric datatypes can be different. If a number of digits in a numeric value exceeds 28, it should be interpreted as a string. If so, check the Load big numeric as string option. Please note that data processing works slower and uses more system resources when numeric values are being converted to string. So, check this option only when it’s really necessary.