Comments
3 comments
-
Hi,
Thanks for your post and sorry you are running into a known issue SDC-1837 "DATETIME2(7) precision off by -.0000001" .
Our development team is investigating this issue and I will update you on any progress we make with this bug.
Only workaround I can suggest is using a less precise DATETIME2 (which is not ideal).
I will keep you posted! -
Hi,
Thanks for your patience.
I am very pleased to tell you that we have fixed the issue you were having in our latest release.
Link to release notes: https://documentation.red-gate.com/disp ... ease+notes
Link to installer: ftp://support.red-gate.com/patches/SQLD ... .0.397.exe
Let me know if this solves the issue for you. -
appears to be working correctly now
Add comment
Please sign in to leave a comment.
For an example, I just synced DB1 to DB2 the same table and SQL Data compare is telling me there is 491 differences in the table... every single one of them is a DATETIME2(7) column...
DB1 according to SQL database compare the value is 2015-03-05 15:33:50.3469999
DB2 according to SQL database compare the value is 2015-03-05 15:33:50.3469998
almost the same but not quite.... that was even after a deployment script made this statement to update that exact row
PRINT(N'Update rows in [Journaling].[JournalEvents]')
UPDATE [Journaling].[JournalEvents] SET [EventDate]='2015-03-05 15:33:50.3469999' WHERE [EventID] = 279254
PRINT(N'Operation applied to 1 rows out of 491')
now the GUI is showing it's different but when I go into the databases and check the values it is showing even more different values...
DB1 in the actual DB: 2015-03-05 15:33:50.3470000
DB2 in the actual DB: 2015-03-05 15:33:50.3469999