ETL and Data Integration tools - Modern ETL software for everyone

Hi

Connected to SQL server

All dates are using the same format setting.

In VI data grid – date column #1 is 12:00:12 AM and correct, date #2 & #3 null, date #4 correct.

After VI import , date column is 12:00:12 PM in the database

Oracle/SQL connection is OLEDB and both source and destination tables have Unique Key.

thanks

Something is wrong with your source connection

There is no such time 12:00:02 AM

It does not make sense

Can we connect to you remotely somehow?

Mike


A.M. and P.M. start immediately after Midnight and Noon (Midday) respectively.

This means that 00:00 A.M. or 00:00 P.M. (or 12:00 A.M. and 12:00 P.M.) have no meaning.

Every day starts precisely at midnight and A.M. starts immediately after that point in time e.g. 00:00:01 A.M. (see also leap seconds)

To avoid confusion timetables, when scheduling around midnight, prefer to use either 23:59 or 00:01 to avoid confusion as to which day is being referred to.

It is after Noon that P.M. starts e.g. 00:00:01 PM (12:00:01)

In my example, the source system is MSSQL and the date via MSSQL window is “2010-11-17 00:00:02.240”.

I agree, there is no 12:00:02 AM, yet that is what the VI data grid is showing.

The select query behind the data grid is using no formatting, yet VI is reading it from MSSQL with 12:00:02 AM.

David

I was under impression that you are loading data from oracle

and I run all my tests against oracle

I will check it with MS SQL

Doing it now,
Mike

I originally was, there is an issue there also.

But I was hit with a MS SQL production issue where the dates are incorrect across mid-night also.

David

David

Reproduced the problem

Looking what can be done about it

Mike