1. This is a Cluster Setup with 6 nodes. Datetime2 column displays the date correctly on 4 nodes. Only 2 nodes exhibit this behavior
2. This is a MS SQL Server 2008 Datasource and they have JRE 7 (shipped OOTB with DV 7.0.3) 
3. Ran the same (below) Query on 2 nodes and the results were different. The incorrect result would have a date backed up by 2 days. So for example, if the one of the date column has value of 1/11/2018 then it would show 1/09/2018 (2 days back) but besides those 2 nodes the rest of the nodes are showing correct date (1/11/2018).

SELECT  --current_timestamp()
c.lastupdated as a, *
FROM /shared/Datetime2/sqltest/waCaptoOpus/waCaptoOpus/captoOpusSummary c
               -FROM /shared/Single_Source/Database_Layer/Databases/CHQ_SQL_FREEDOMDW/waCaptoOpus/waCaptoOpus/captoOpusSummary c
 	-/services/databases/SINGLE_SOURCE/FREEDOMDW/WACAPTOOPUS/CAPTOOPUSSUMMARY c
WHERE 
c.account='8499050120096983'

4. Ran this Query from a View and also ScratchPad. Both exhibit the same behavior (As reported in Step 3)
5. Compared the following on the node where data is incorrectly displayed to the node where data is correctly displayed
• Capabilities files 
• microsoft_sql_server_2008_values
• Execution Plans
• Lineage 
• Server_values.xml 
They are all identical. 

6. Suspected that it might be a driver issue and compared the SQLJDBC4.jar file sizes on these nodes. They matched as well.
7. Copied the sqljdbc4.jar file from a working environment into a non-working environment. Restarted the services and attempted to run the Query. That displayed incorrect results as well.
8. This issue is ONLY happening in Production cluster. Rest of the environments seem to be working fine.
9. I did more research and found that there was a similar issue with MS SQL Server 2008 JDBC driver version 3 and JRE 7. In this case, customer is using SQLJDBC4. 
11. Requested the customer to try with the latest JDBC jar file. Customer attempted SQLJDBC41.jar in a non-PROD environment but he was unable to establish a mere Test connection. Hence, he was reluctant to test this on Production environment.