March 26, 2025 at 11:40 am
I'm using an ADO Net Source to extract data and running into an issue with timestamps changing before reaching the destination. I can log directly into the source system and see a value should be 2025-03-01 00:03:14 but SSIS is brining it back as 2025-03-01 01:03:14. I put a data viewer on it so this is happening before any conversion or importing to SQL. Any idea why this is and what can be done to make sure the value in the source system is always the value we get?
March 26, 2025 at 11:46 am
Presumably this is in SSIS?
What is the source system? Are you sure that the value, at database level (rather than when viewed through an app, for example), is as you say? Could there be a time zone issue involved?
March 26, 2025 at 12:08 pm
Yes, it's SSIS.
The source system is hadoop. We thought about the possibility of time zone issues but we've tested in two different time zones and still got the result of 2025-03-01 01:03:14. It seems to be consistent adding an hour to the time no matter what time zone we are using.
March 26, 2025 at 3:38 pm
I know nothing about Hadoop, sorry. Have you determined that the value you are expecting to see (2025-03-01 01:03:14) is exactly what is stored in the Hadoop database and hasn't gone through any sort of process which could have changed it?
As the value you are seeing in different time zones is unchanging, it suggests that this is the correct or native one (as stored in the DB).
March 26, 2025 at 3:56 pm
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy