Issue comparing field values of type real equal to 0
SQLAdminCJ
Posts: 17
Hello,
I am having an issue with the SDK where it is generating diff queries to set real field values equal to 0 that already appear as 0 in both databases (i.e. this field is being registered as different when it is not different).
Perhaps, since the fields are of type real, they contain very small numbers that are appearing as 0 in SQL Server Management Studio?
In any case, how do I avoid having the SDK consider these fields different? Is there a parameter I can set? Please advise. Thanks.
I am having an issue with the SDK where it is generating diff queries to set real field values equal to 0 that already appear as 0 in both databases (i.e. this field is being registered as different when it is not different).
Perhaps, since the fields are of type real, they contain very small numbers that are appearing as 0 in SQL Server Management Studio?
In any case, how do I avoid having the SDK consider these fields different? Is there a parameter I can set? Please advise. Thanks.
Comments
We've had issues in the past with FLOATs where a difference is seen due to SQL Data Compare not using the full precision when comparing. We added a comparison option in V10 to use the full precision and it looks like you can utilise this in the SDK too:
Not sure if this works for REAL though; but it's worth a try...
Redgate Software