March 1, 2010 at 3:10 am
Hi
I know in DTS this could have been considered a flaw, but it used to implicitly convert data types. For example a staging table with a char would convert to an int in the destination of a transform.
I realise in SSIS you can use the data conversion transformation, but each column must be done manually and individually. This is totally unrealistic for large imports - i.e. the 2209 column worth of text files im working on.
Is there not a way to "turn on" implicit data type conversion, or more ideal would be to somehow get the data conversion transformation to use the destination data types as the conversion type automatically.
So far the easiest solution seems to be to write dynamically create the select statement for the oledb source from system tables and code a convert or cast into it.
Seems like quite a limitation using it for larger scale imports. l already had to overcome the import of the text file defaulting all columns to char 50 or inaccurately determining the type by manually creating a load of dummy text files with the colums padded with characters to the correct length! Ive had to do more manual workarounds in this one package than any DTS I have written!
Grrrrr.. ok i'm done grumbling. Anyone help?
March 1, 2010 at 3:49 am
OK, so I started writing a query to construct the select statement. Now the editor window for a sql command on oledb source truncates the query!
Ill have to use an SP for the select... gets better by the minute!
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply