Strange problem with DataReaderSource

Hi there,
I have a very strange problem with DataReaderSource.
I'm trying to get data from InterBase table. I created a Connection manager and the connection was successful. The SQLCommand in "Component properties" tab is a simple "select * from <table_name>". When I switch to the "Column mappings" tab, only the first column from the table is displayed.
Pressing the "Reftesh" button resulst in the following error:
Error at Data Flow Task {DTS.Pipeline]: The "output column <column_name> has a length that is not valid. The length must be between 0 and 4000.
When I go to the "Input and Output Properties" tab, the DataType for the output column is not populated and the error message "Error in Data Flow Task [DTS.Pipeline]: The output column <column_name> had an invalid datatype (0) set."
The DataType property is not populated at all. Changing it to DT_STR results in error:
"Property value is not valid". Details: Error at Data Flow Task [DataReader Source]: The data type of output columns on the component "DataReader Source" cannot be changed".

Any idea what's going on here

Answer this question

Strange problem with DataReaderSource

GirishP
Hi Brent,
Thanks for your reply.

In "Column mappings"time I have the same column in both "Available External Columns" and "Available Output Columns" lists and they are not connected. When I map them, I get that error saying that "the output column had an invalid datatype value (0) set".
Both, External and output column had no datatype set after the Connection Manager has been selected from that dropdown list. I can change the datatype for the External column to String (DT_STR), but when I change the datatype for the Output column, it comes up with the following error: "Propery value is not valid" and "The data type of output columns on the component "DataReader Source" (48) cannot be changed." in the Details window.

The other problem is that only the first column is reported, although "select * from table_name" is entered as SQLCommand.

We have an Access database with tables linked to the tables from the InterBase database and there is no problem with it: all the columns are included and mapped.

Any further thoughts will be much appriciated.
Lee.NET
There seems to be a problem with the data reader source pulling the metadata from InterBase. Can you try explicitly converting your datatypes on the columns in your query (ex. "select convert(varchar(50), <column>)") You might also try an oledb connection if there is a driver available in case it's a bug with the data reader source.
reom
It looks like a column in your source has a length that exceeds what sql allows.

What does the metadata look like for that column in the "external columns" in the "input and output properties" tab The data reader source should be mapping the "output colum" to the same data type and length as that.
emates

The DataReader source is a bit lax with data types, basically it goes through managed types and that means it can loose some semantics on the way, at least that is the way I see it. You may be encountering this, or perhaps the Interbase provider itself is not very accurate with the metadata it exposes. Some more info on this theme from an issue I had-

Re: DataReader Source and Column Types - MSDN Forums
(http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=278744&SiteID=1)
Strange problem with DataReaderSource

Answer this question