SAP Knowledge Base Article - Preview

2607863 - Seconds and milliseconds are truncated when loading SQL Server datetime2 field - Data Services

Symptom

  • BODS cannot load correct date values to SQL Server.
  • DATETIME2 field not loading correctly.
  • No seconds or milliseconds are being loaded by Data Services to datetime2(7) field.
  • sysdate() seconds and milliseconds are truncated.
  • All seconds and milliseconds are set to 0 when loaded to SQL Server 2016 datetime2(s) field.
  • When loading the sysdate() to datetime field, seconds and milliseconds are loaded correctly, but requirement is to use datetim2 field.
  • Seconds and milliseconds are removed when loading a SQL Server table.
  • If loading the same SQL Server table using an insert statement from within SQL Server Management studio, the seconds and milliseconds are not removed or set to zero, just when loading from Data Services.


Read more...

Environment

  • SAP Data Services
  • Microsoft SQL Server 2016

Product

SAP Data Services all versions

Keywords

KBA , EIM-DS-EXE , Job Execution , EIM-DS , Data Services , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.