Execute SQL Task Error

Hot Topic

File growth problem in 2005
Reattaching old database
Will SQL Express run on Win2k3 Web Edition?
Yet Another SQL Server Express 2005 April CTP install failure
Obscure error while attempting to install SQL Server 2005 SP1
SQL Server 2005 Sep CTP setup failed.
Running SSIS Packages in Management Studio
Cannot get the Service Broker work
The parameter is incorrect. (Microsoft OLE DB Provider for Visual FoxPro) after SP1
Problems installing SQL 2000

SQL Server

Scale issue with oracle Numeric types and OLEDB or datareaders
An incorrect or unsupported HTTP function call was made error
How to check if the file exists or not before bulk insert
Problem with CASE Expression
Beginner question Searching table
calculated dimension question
query analyzer does not run
Stuck between "Failed to generate user instance" and "An attempt to attach...failed"
can we automate the data mining models management?
Integer identity value handling in export / import

Execute SQL Task Error

I have a stored procedure that accepts an integer as
input and sends a value out as type varchar(600).

When I use Execute SQL task with ADO.Net or ADO Connection
Manager and assign proper values for the parameters and
their direction, the execution of the task returns ONLY 1
character (first character)for the output parameter.

Sounds like a bug since I can't set the string length
anywhere in the data type.

Any help/work arounds would be greatly appreciated it.

Thanks

Answer this question

Execute SQL Task Error

  • Iyyappan.A

    This is a shot in the dark, but maybe a UCS-2 string (Microsoft's favorite type of Unicode encoding) is being used, and being interpreted as one of the Windows proprietary 8-bit encodings (eg, windows-1252), and the first character is in the ASCII set (eg, a regular letter), so the second byte of its UCS-2 representation is a zero byte, and this is truncating the string.

    If you don't follow that, perhaps try changing the return value to nvarchar(600).

    Note however, that we're successfully passing back varchar values via Execute SQL
    tasks.

  • Trish

    N.S. Which build you were on
    Another possibility is if you were on an earlier build, we had a known issue using ADO.Net connection in ExecuteSQLTask to get the full string value from out parameters. If that's the case for you, try upgrade to our CTP16 release and you should see the fix.

    Thanks

  • Venkata Veeraraghavan

    I am on Version 8.0.50215.44. I'll upgrade to CTP 16. Thanks.
  • Execute SQL Task Error
Answer this question