Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Getting Output value from sp_executesql for XML issue Expand / Collapse
Author
Message
Posted Tuesday, October 30, 2012 5:13 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 2:44 AM
Points: 50, Visits: 306
Hi,

I am trying to get an xml blob into a var from dynamic sql. However, whenever I run this:

DECLARE @tApplXML XML
,@SQL NVARCHAR(max)
,@ParmDefinition NVARCHAR(1024)
,@applnbr int

set @applnbr = 24

SET @SQL = N'SELECT * FROM [database].[dbo].[table]
WHERE [ApplNbr] = @pApplNbr
FOR XML PATH(''database.table'')'
SET @ParmDefinition = N'@pApplNbr INT,@ptApplXML xml OUTPUT'

EXECUTE sp_executeSQL
@SQL,
@ParmDefinition,
@pApplNbr = @ApplNbr,
@ptApplXML= @tApplXML OUTPUT

select @tApplXML

Firstly I get the XML returned from the OUTPUT , then I get a NULL value. I need @tApplXML to retain the XML value. But whatever I try I cant seem to get it to work....

Can anyone point me in the right direction?

Many thanks, Phil


Post #1379087
Posted Wednesday, October 31, 2012 7:25 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 6:03 PM
Points: 3,609, Visits: 5,221
Try this:

DECLARE @tApplXML XML 
,@SQL NVARCHAR(max)
,@ParmDefinition NVARCHAR(1024)
,@applnbr int

set @applnbr = 24

SET @SQL = N'SELECT @ptApplXML = (SELECT * FROM [database].[dbo].[table]
WHERE [ApplNbr] = @pApplNbr
FOR XML PATH(''database.table''))'
SET @ParmDefinition = N'@pApplNbr INT,@ptApplXML xml OUTPUT'

PRINT @SQL

EXECUTE sp_executeSQL
@SQL,
@ParmDefinition,
@pApplNbr = @ApplNbr,
@ptApplXML= @tApplXML OUTPUT

select @tApplXML





My mantra: No loops! No CURSORs! No RBAR! Hoo-uh!

My thought question: Have you ever been told that your query runs too fast?

My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.


Need to UNPIVOT? Why not CROSS APPLY VALUES instead?
Since random numbers are too important to be left to chance, let's generate some!
Learn to understand recursive CTEs by example.
Splitting strings based on patterns can be fast!
Post #1379579
Posted Wednesday, October 31, 2012 7:41 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 2:44 AM
Points: 50, Visits: 306
Thanks so much. Its embarrassing, thats so simple. I couldn't see the wood for the trees
Post #1379581
Posted Wednesday, October 31, 2012 7:45 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 6:03 PM
Points: 3,609, Visits: 5,221
No need to be embarrassed and you're welcome.

You'd be surprised how often the simplest issue is uncovered quickly by a second set of eyes. In this case, I happened to have done a lot of dynamic SQL of late so the answer kind of jumped out at me.

And it helped a lot to have code that was easily modified to run on my SQL.



My mantra: No loops! No CURSORs! No RBAR! Hoo-uh!

My thought question: Have you ever been told that your query runs too fast?

My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.


Need to UNPIVOT? Why not CROSS APPLY VALUES instead?
Since random numbers are too important to be left to chance, let's generate some!
Learn to understand recursive CTEs by example.
Splitting strings based on patterns can be fast!
Post #1379582
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse