2
Vote

DT_DBTIME2 not supported

description

In some cases this component seems to null some fields. See the attachments of an example where the incoming field is showing non-null and the output is null - this is on a field that has no conversion wanted and is included in output.
 
I ended up using convert in sql to work around, but could this be investigated.
 
This is due to DT_DBTIME2 not being supported - check for all types when fixing this issue...

file attachments

comments

00 wrote Nov 22, 2010 at 9:51 AM

see setup

00 wrote Nov 22, 2010 at 10:56 AM

The characteristics of this example where that there were 6 million records from the source and it was feeding into a Kimball SCD component. I think that it always seemed to be the xth column that was affected. initially it was a datetime column that I was converting that had this behaviour but in troubleshooting I deleted and added a new RDC component - and I think the columns had changed order from the source, so maybe it isn't about the number of rows, maybe a number of columns?.. I will keep my eye out on my travels for a definate repro.

00 wrote Nov 22, 2010 at 10:58 AM

sorry I said 6 million, it was actually 15 million records

00 wrote Nov 22, 2010 at 6:07 PM

I think that actually this may be relating to the new time/date datatypes. I have a time(0) field which it isn't dealing with correctly. Maybe this is the problem? It has caused problems with other compoenents

toddmcdermid wrote May 3, 2011 at 10:03 PM

I don't have support for the DT_DBTIME2 data type in there. Relatively easy to add... I'll see what time I can scrape up.

wrote May 3, 2011 at 10:04 PM

wrote May 17, 2011 at 12:10 PM

DanielBos wrote May 17, 2011 at 12:11 PM

I have the same problem with 20 million records...

DanielBos wrote May 18, 2011 at 7:01 AM

I have the same problem with DT_DBTIMESTAMP2. A workaround is to make the input column of the DT_DBTIMESTAMP type, then the Replacing Data Conversion component can cope with it.

wrote Feb 13, 2013 at 9:31 PM