Options
DATETIME2(4) precision issue
mikelt21
Posts: 2
Hi,
I have 2 databases, one running on SQL Server 2016 (13.0.1601) and the other running on SQL Server 2012 (11.0.6020). When comparing 2 tables (one on each server) which are supposed to contain the same data I've been noticing an issue with some of the datetime2(4) fields. When inspecting both tables in management studio the datetime2(4) fields have the same value (ex. "2016-03-02 16:02:48.0451"). However, when doing a redgate data comparision the comparison sdk creates an update statement modifying the target db's value to "2016-03-02 16:02:48.0452". I'm using SQL Comparison SDK 11.5.2. Everything diffs correctly when I compare a 2012 db with a 2012 db or a 2016 db with a 2016 db. This only happens to some of the rows but not all.
Any help would be greatly appreciated. Thank you.
Mike
I have 2 databases, one running on SQL Server 2016 (13.0.1601) and the other running on SQL Server 2012 (11.0.6020). When comparing 2 tables (one on each server) which are supposed to contain the same data I've been noticing an issue with some of the datetime2(4) fields. When inspecting both tables in management studio the datetime2(4) fields have the same value (ex. "2016-03-02 16:02:48.0451"). However, when doing a redgate data comparision the comparison sdk creates an update statement modifying the target db's value to "2016-03-02 16:02:48.0452". I'm using SQL Comparison SDK 11.5.2. Everything diffs correctly when I compare a 2012 db with a 2012 db or a 2016 db with a 2016 db. This only happens to some of the rows but not all.
Any help would be greatly appreciated. Thank you.
Mike
Comments
Sorry to hear you're experiencing this issue. If you upgrade to the latest version of the SDK, does that help? Here's a download link - ftp://support.red-gate.com/patches/SQLC ... 5.7.77.exe
Redgate Software