Showing posts with label component. Show all posts
Showing posts with label component. Show all posts

Sunday, February 26, 2012

Error in Derived Column component

I am getting this error,

[Derived Column [192]] Error: Converting an input column from type DT_STR to type DT_WSTR failed. An error occurred while performing the implicit conversion on the input column.

But I don really understand y there is a attempt to type cast at all ?

Please advise ....

thanks in advance

The expression evaluator almost always implicitly converts DT_STR columns to DT_WSTR, because all string functions are implemented for Unicode only. There are only a couple very specific exceptions.

You might try to putting a data conversion transform in your flow and doing an explicit convert from DT_STR to DT_WSTR for that column and see if you get a more helpful error message. Or, redirect that row to an error output, and inspect the data and post it here.

Thanks
Mark

|||

Mark Durley wrote:

You might try to putting a data conversion transform in your flow and doing an explicit convert from DT_STR to DT_WSTR for that column and see if you get a more helpful error message.

I thought of this earlier and when I tried with a Data Conversion Component, I was not able to locate an option as DT_WSTR. Am I missing something here?

thanks for the Help so far...

|||

In the Data Conversion transform UI, in the Data Type drop down, you should see an option:

Unicode string [DT_WSTR]

Mark

|||

In the column marked Data Type in your Derived Column Shape change the value from Unicode [DT_WSTR] to string [DT_STR]

Does this answer your question?

|||Thx for the reply :)

Friday, February 24, 2012

Error in create sp

hi every one

when i want to create a stored procedure that contain character " with a ado component , i receive this error message :

'Parameter object is improperly defined. inconsistent or incomplete information was provided.'

but if i create this procedure from query analyzer , this sp creates successfuly.

whyyyyyyyyyyyyyyyy? :mad:My guess would be that the client side (probably VB) code doesn't properly escape the quotation mark, and since the Transact-SQL doesn't need to escape the quote it isn't a problem there. I'd suggest that you post the VB code you are using so that we can see if that is your problem.

-PatP|||It's the QUOTED_IDENTIFIER setting on connection object vs. your QA. On the client side set this setting to be the same as in QA (in Connection Options menu item in QA).