Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SSIS and Import/Export (2005)
 Warning message in SSIS pkg(wiered)..

Author  Topic 

Ravi0435
Starting Member

47 Posts

Posted - 2009-04-30 : 17:11:28
Hi all:
IN SSIS pkg, i get the following errors.
I know the folloiwng 3-errors suggest that the Source column datatype is larger then the destination column, But thats not the case...infact both have same table structure, as the destination table is archive table which stores all the data old data from the parent table.

source(700) and destination(700)
WHY DOES THIS HAPPEN..??

I am trying to use Data Type Conversion to convert them back to 700 so as to eliminate the warning.
source(700)--> SSIS(2000)-->ConversionTo(700)--> destination(700)
Warnings:
--------

Warning 1 Validation warning. Message to Msg_arc: Msg_arc [1]: Truncation may occur due to inserting data from data flow column "subject" with a length of 2000 to database column "subject" with a length of 700. Archive_Messages.dtsx 0 0


Warning 2 Validation warning. Message to Msg_arc: Msg_arc [1]: Truncation may occur due to inserting data from data flow column "recipient_address" with a length of 2000 to database column "recipient_address" with a length of 700. Archive_Messages.dtsx 0 0


Warning 3 Validation warning. Message to Msg_arc: Msg_arc [1]: Truncation may occur due to inserting data from data flow column "recipient_cc_address" with a length of 2000 to database column "recipient_cc_address" with a length of 700. Archive_Messages.dtsx 0 0


thanks,
Ravi



Nothing much that i can do..!!

vijayisonly
Master Smack Fu Yak Hacker

1836 Posts

Posted - 2009-05-01 : 10:02:05
quote:
source(700)--> SSIS(2000)-->ConversionTo(700)--> destination(700)


why do you have the SSIS with 2000 in the middle? whats that?Can you explain the flow in your package.
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2009-05-01 : 10:37:00
Check the metadata.
Sounds like the columns imported were 2000 bytes at one time (maybe by copying a package?) and it hasn't been updated.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

Ravi0435
Starting Member

47 Posts

Posted - 2009-05-01 : 16:26:50
quote:
Originally posted by vijayisonly

quote:
source(700)--> SSIS(2000)-->ConversionTo(700)--> destination(700)


why do you have the SSIS with 2000 in the middle? whats that?Can you explain the flow in your package.





No - thats just the Length i am indicating:

From Source where the length of the column is 700(nvarchar) ..once i point SSSIS OLEDB Source it shows that column as length 2000(nvarchar) and then i have to use data type conversion task to convert it back to 700(nvarchar) and then load in the destination.

hope i am clear..sorry for the confusion

Nothing much that i can do..!!
Go to Top of Page

Ravi0435
Starting Member

47 Posts

Posted - 2009-05-01 : 16:56:06
thanks guys for the answers...just remove the tasks/transformations and re-map them:

the following link may also help you..

http://bi-polar23.blogspot.com/2008/05/checking-ssis-data-flow-metadata.html



Nothing much that i can do..!!
Go to Top of Page
   

- Advertisement -