topic Re: Talends Refusal to load a date into SQL in Talend Studio

Talends Refusal to load a date into SQL

Anonymous — Tue, 13 Nov 2018 19:24:36 GMT

I've been at this all day at this point. I am receiving a date in string form, yyyymmdd, that I used java to convert. I then connect to a tMap where it is specified as a date and will not work as a string, I checked, confirming it's a date and looking at it with a tLogRow, it is returning a date mm/dd/yyyy. However, when I connect to my tsqldwoutput and try to load a date field, it says:

SQLServerException: Conversion failed when converting date and/or time from character string.

This directly contradicts everything Talend is doing, so why is it trying to convert and obvious date to a string? Below you can see the 04/10/2018 the tLogview shows. Help!!!

Re: Talends Refusal to load a date into SQL

Anonymous — Wed, 14 Nov 2018 06:01:37 GMT

Hi,

Could you please share the screen shot of overall job flow and the component screenshot (including schema) of both tmap and the SQL Server output component?

I believe the column has been accidentally categorized in wrong data type in one of the components.

Warm Regards,

Nikhil Thampi

Re: Talends Refusal to load a date into SQL

Anonymous — Wed, 14 Nov 2018 12:48:03 GMT

I was able to get it to work eventually, however I had to delete my SQL
table and let Talend create it. It created the same table with same schema
and data types. Not sure what was wrong. I triple checked everything and
verified that it was actually producing what I needed, it was extremely
frustrating but I finished it. Thank you for the reply.

Re: Talends Refusal to load a date into SQL

Anonymous — Wed, 14 Nov 2018 13:09:13 GMT

@Courtneylane77

Sometimes the manually created DDL format syntax differs from Talend auto generated Table syntax.

Since Talend is already aware of the data types and format patterns, it will choose the syntax correctly. It has happened to me also in the past where I had created the structure manually and it was not working due to format problems.

I am happy that you have resolved the issue and moving forward. Could you please close the topic as it will help the other community members in future?

Warm Regards,

Nikhil Thampi