January 23, 2009 at 8:03 am
I am converting a number of SS00 DTS packages in my ETL system to SS05 SSIS. They copy a flat file as text fields into a load table, which a stored procedure then processes. The SSIS Flat File Connection Manager needs to copy the fields into char fields in the load table, but many of the fields are predominantly numbers. When I move the package it seems to be reverting the data to a different datatype, usually DT_I4 (4-byte signed integer) based on scanning the first 200 records. But a few of the thousands are garbage, and the DT_I4 will not load to a char(6) field.
Can I "lock" the connection manager so that SSIS will not change? How can I keep the package stable when moving between systems? Or is there another approach?
Thank you for your help.
January 23, 2009 at 8:29 am
Hi,
I don't fully understand what you mean by "moving between systems"...maybe you can elaborate.
Aside from that, the connection manager has properties for every column and you can specify explicitly what the datatype for every column is.
January 23, 2009 at 1:37 pm
I created the packages on my desktop using BIDS and saved them to a server, using "save as". Evey column was defined, with name, length, and a type of DT_STR. When importing the package to another server, using BIDS on the server, the datatype and length gets clobbered.
I'm struggling with managing packages. I've seen little of use written about all the XML files produced, how to manage them, move them, use one VSS folder from a two different platforms. Very frustrating when a few hours work is destroyed trying to save a package.
Thanks for your time and any help -
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply