|
||||||
| BI Monkey BI Monkey is the ‘nom de plume’ of James Beresford, a Certified Microsoft BI Professional and MBA living and consulting in Sydney |
 |
|
|
LinkBack | Thread Tools | Display Modes |
16th September 2009, 07:40 PM
|
#1 (permalink) |
|
Senior Member
Join Date: Jun 2009
Posts: 62
 |
SSIS Derived Column forcing data type changes
In SQL 2005, the Derived Column Transformation used to drive me nuts because any time you changed a string value, the component automatically changed the datatype to Unicode, even if it was originally string. This meant any time you changed an Expression that returned a non-unicode string, you had to change it back.
In SQL2008 it has got worse! Now the same change of data type is forced on you, but now the only way to change the data type back is to go into the Advanced Editor and amend the data type of the Output Column there, because – apparently by design – the data type is now locked in the normal UI. Why by design? No idea, but according to this Connect article, that’s the way it’s going to stay – please vote this up and maybe Microsoft will revisit this incredibly annoying “feature”. Get More from the original blog... |
|
|
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| The Derived Column Transformation | James Beresford | BI Monkey | 1 | 3rd September 2009 12:55 PM |
| The Slowly Changing Dimension Transformation, part 2 ? Type 2 Dimensions | James Beresford | BI Monkey | 0 | 11th August 2009 12:58 PM |
| Flat File Sources and the Decimal Data Type | James Beresford | BI Monkey | 0 | 27th July 2009 08:22 PM |
| Flat File Source Error: The column delimiter for column [ColumnName] was not found | James Beresford | BI Monkey | 0 | 30th June 2009 12:21 PM |
| The Copy Column Transformation | James Beresford | BI Monkey | 0 | 25th June 2009 10:12 PM |
|
|
|
|
|
|
Linear Mode
