topic Re: Transfer DATA from a DB SQL table to a delimited file. IS IT POSSIBLE? in Talend Studio

Transfer DATA from a DB SQL table to a delimited file. IS IT POSSIBLE?

Anonymous — Mon, 13 Aug 2018 13:06:27 GMT

Hi everybody,

I am trying to transfer data from a DB SQL table to a delimited file.

I have a message as follows in the picture below.

Thanks

Gaviota

Re: Transfer DATA from a DB SQL table to a delimited file. IS IT POSSIBLE?

Anonymous — Wed, 15 Aug 2018 08:13:58 GMT

Hi,

It happens because the data type in your Talend column (String) is slightly different from the DB data type (Varchar2). But the conversion will happen automatically in this case and you can safely extract the data from the source.

Could you please try and let us know whether you were able to extract data?

Warm Regards,

Nikhil Thampi

Re: Transfer DATA from a DB SQL table to a delimited file. IS IT POSSIBLE?

Anonymous — Mon, 20 Aug 2018 08:41:19 GMT

Hi Nikhil,

thank you in advance for your answer.

So, I am working with the DB AdventureWorks2012. I have this DB in SQL, I have the Product Table there. Then, I am trying to transfer the data from SQL Product Table to a delimited file. I already created the connection using Metadata.

The data from SQL Product Table is transferred to a delimited file but always this message of something wrong appears in the source.

So, here some pics of my job.

Thanks for your help!

Gaviota

Re: Transfer DATA from a DB SQL table to a delimited file. IS IT POSSIBLE?

iamabhishek — Mon, 20 Aug 2018 13:45:18 GMT

@Gaviota - the table [Production].[Product] you are referring here has used MONEY datatype for two columns (StandardCost & ListPrice) and User Defined Data Type for three other columns (Name - Name which is of NVARCHAR and MakeFlag & FinishedGoodsFlag which are of BIT). Now from your screenshot below I see these are the columns which have been highlighted due to your error.
Just define the db type and destination type as as BIT and BOOLEAN for MakeFlag & FinishedGoodsFlag

NVARCHAR with length 50 as db type and String as destination type would do for Name.

For StandardCost & ListPrice make the db type as MONEY and use BigDecimal as destination type as BigDecimal is the best type for representing currency decimal values.

I hope this would solve your problem with the issues that you reported.