DATETIME2 precision issues

msnelling

Hi,
SQL Source Control 4 identifies static data rows as different when they have a column of DATETIME2. For instance rows are stored in source control with the value '2014-01-10 11:35:10.2859999' but when viewed in the table they are reported as '2014-01-10 11:35:10.2859998'.

Rob C

Hi,

Sorry about this. This is a bug with reference SDC-1744. Unfortunately I don't currently have a timeframe for when this will be fixed.

msnelling

Umm ok, so that kind of renders SQL Source Control useless for us now.

Rob C

I've just had an update from the development team. The team are current working on a fix in the engine and as soon as this is done, the engine can be pulled into SQL Source Control. I imagine that it'll likely be 3-4 weeks before there's a release that contains a fix, but I'll let you know when I hear more information.

Rob C

Hi,

The latest version of SQL Source Control contains the fix for this issue. Could you try it and verify that it fixes the problem for you? Here's a download link if you need it - ftp://support.red-gate.com/patches/SQLS ... .3.575.exe

Thanks.