Wrox Programmer Forums

Need to download code?

View our list of code downloads.

| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: Professional SQL Server 2005 Integration Services ISBN: 0-7645-8435-9
This is the forum to discuss the Wrox book Professional SQL Server 2005 Integration Services by Brian Knight, Allan Mitchell, Darren Green, Douglas Hinson, Kathi Kellenberger, Andy Leonard, Erik Veerman, Jason Gerard, Haidong Ji, Mike Murphy; ISBN: 9780764584350
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional SQL Server 2005 Integration Services ISBN: 0-7645-8435-9 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old February 9th, 2006, 10:44 AM
Registered User
 
Join Date: Feb 2006
Location: , , .
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Chapter 6 "Using SQL Output Parameters..."

on pages 148-150 i'm trying to do the exercise and am getting the following error--

[Execute SQL Task] Error: Executing the query "EXEC usp_GetConfigParamValue 'MYAPP','MYPARM','STRING',@MYVALUE OUTPUT" failed with the following error: "The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 3 ("@MyValue"): Data type 0xE7 has an invalid data length or metadata length.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

i've rechecked everything several times...anyone run into this or know what might be the problem?

thanks

burke
Reply With Quote
  #2 (permalink)  
Old February 11th, 2006, 03:52 PM
Registered User
 
Join Date: Feb 2006
Location: Montreal, Quebec, Canada.
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I got the same problem. And if I try the exercise available that you can download from Wrox, it doesn't work either. So the problem seem's to be a difference between the version of SQL 2005 they use to create that exercise, and the way to do it in the final version...
Reply With Quote
  #3 (permalink)  
Old February 11th, 2006, 06:23 PM
Registered User
 
Join Date: Feb 2006
Location: Montreal, Quebec, Canada.
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi,

I made some test and it work, but not for a string return:

I change the stored proc to this:
ALTER PROCEDURE [dbo].[uspGetConfigParamValue]
    @ApplicationName varchar(30),
    @ParameterName varchar(50),
    @ParameterTypeName varchar(30),
    @ParameterValueVar int OUTPUT
AS
BEGIN
    SET NOCOUNT ON;
    SET @ParameterValueVar = 55
END

and I change the Execute task to this:
SQLStatement: dbo.uspGetConfigParamValue
IsQueryStoredProcedure: True

I declare the 4 variables in the parameter mapping, and I use the same name as in the stored Proc(see http://www.juliankuiters.id.au/artic...put-parameters), like @ParameterValueVar map to MyFile as a Int32 (for the purpose of testing). So I have also 4 variables in the package (MyFile as Int32, MyApp, MyParm and MyType as String).

Now, I change the expression for the connection as:
"C:\\Test" + (DT_STR, 2, 1252) @[User::MyFile] + ".txt"

and it work, it change the name of the file. But when I try to use string type, it give me the same error (data type invalide). So I think that maybe the String type of the variable at the package level is not compatible with the string type in the ADO.NET connection.
Reply With Quote
  #4 (permalink)  
Old February 14th, 2006, 03:33 PM
Registered User
 
Join Date: Feb 2006
Location: , , .
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I'm getting the same error and have played around with it trying to get it to work - but no luck yet. Anyone else?

Reply With Quote
  #5 (permalink)  
Old February 22nd, 2006, 07:31 PM
Registered User
 
Join Date: Feb 2006
Location: Auckland, , New Zealand.
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Anything Further on this?

Its something i want to use in the Data warehouse i am developing, and it not working is quite frustrating.


Thanks,
Truby Gravatt
Aspex Consulting Ltd
e: truby@aspexconsulting.co.nz
Reply With Quote
  #6 (permalink)  
Old February 28th, 2006, 04:46 PM
Registered User
 
Join Date: Feb 2006
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I reported this bug last week and they have advised that a fix should appear on the website within the next week.

Reply With Quote
  #7 (permalink)  
Old March 5th, 2006, 08:11 PM
Registered User
 
Join Date: Feb 2006
Location: , , .
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I'm having the same issue. Where on the website will the fix appear?
Reply With Quote
  #8 (permalink)  
Old March 5th, 2006, 10:41 PM
Registered User
 
Join Date: Feb 2006
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi Mark,

I received the response from Wiley Customer Support on 1st March.
They said the solution should appear at the following link.

http://www.wrox.com/WileyCDA/WroxTit...764584359.html

Jays

Reply With Quote
  #9 (permalink)  
Old March 6th, 2006, 04:42 PM
Registered User
 
Join Date: Feb 2006
Location: , , .
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks Jays
I'll keep checking it...
Reply With Quote
  #10 (permalink)  
Old March 8th, 2006, 11:20 AM
Authorized User
 
Join Date: Jan 2006
Location: , , .
Posts: 10
Thanks: 0
Thanked 0 Times in 0 Posts
Default

In case anyone is interested. I found a mechanism for getting return values out of parameters when making OLEDB calls to stored procs.
Instead of calling the proc through this mechanism, 'EXEC ? = proc', you call it this way '{? = CALL proc}' it works. You can simply map a parameter to the return value of the proc referencing a parameter called '0'.
There's been a lot written up around this in various places on the web. I found the solution here:
http://msdn.microsoft.com/library/de...qlprovspec.asp


Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Output Parameters: I can't be this stupid... raysot BOOK: Professional SQL Server 2005 Integration Services ISBN: 0-7645-8435-9 13 May 20th, 2010 07:28 PM
output parameters with the objectdatasource trancehead ASP.NET 2.0 Professional 2 August 25th, 2008 12:41 PM
Output Parameters Bob Bedell SQL Server 2000 2 March 25th, 2006 06:32 AM
OUTPUT Parameters saulodet ADO.NET 0 May 14th, 2004 10:02 AM
SQL output parameters ohiggs SQL Server 2000 4 February 9th, 2004 10:09 PM



All times are GMT -4. The time now is 03:45 AM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.