MSSQL Date columns Change Value when Imported


After running an Import Job that is connected to a Microsoft SQL database, the Date type data columns are imported with the incorrect date values. For example, Microsoft SQL shows "Mar. 1, 2010" for a particular row, but Datameer shows "Mar. 3, 2010" for this same row.


This is an issue with the Microsoft SQL JDBC driver that was used in the environment. Unfortunately, the exact build number of the affected drivers is unknown.


To resolve this issue, update the JDBC driver to the latest version that is available from Microsoft. 

Alternatively, consider using an alternative JDBC driver for this database connection. For example, jTDS provides third party Microsoft SQL drivers which are available here: