Postgresql destination data truncation issue in SSIS

pandiyanrajendran rajendran 1 Reputation point
2021-02-25T15:22:58.163+00:00

Hi All,

My Source is SQL and Destination is Postgresql.
I have column called Personal_ID as Varchar() datatype and in Destination i have Text(Unicode text stream) data type.

so I have used data convertion to convert the data type DT_WSTR to DT_NTEXT.

but SSIS package is running fine but data not inserting properly.
I have values like "123456" in the source but in destination am getting only "1(first character)"
Its happenning only when am moving the data to PostgreSQL.**

Note:Am using intellisoft oledb provider to connect the postgresql.

Thanks in advance

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,339 questions
SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,523 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Monalv-MSFT 5,896 Reputation points
    2021-02-26T08:17:19.057+00:00

    Hi @pandiyanrajendran rajendran ,

    Please check the data type of column in Postgresql Destination.

    If the length is short in destination, please add length in the data type.

    Best regards,
    Mona

    ----------

    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Tom Phillips 17,721 Reputation points
    2021-02-26T14:43:06.14+00:00

    What exactly is in your data conversion task?


  3. sreekanth mohan 1 Reputation point
    2021-10-06T19:11:15.223+00:00

    NVARHAR(DT_WSTR) can be mapped to TEXT(DT_NTEXT) in the OLEDB Destination but you need to make "Validate External Meta Data" property of the destination to "False".
    I know Pandiyan got this work around. This might be helpful for some one so posting it here.

    0 comments No comments