This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 31%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENN%3C/text%3E%3C/svg%3E)
I have a complex procedure returning one result set.
However, when I execute using WITH RESULT SETS I'm getting this error:
Msg 11535, Level 16, State 1, Procedure im_automation.accent_changes, Line 814 [Batch Start Line 0]
EXECUTE statement failed because its WITH RESULT SETS clause specified 1 result set(s), and the statement tried to send more result sets than this.
I'm not understanding why I'm getting such error. The procedure returns just a single query.
im_automation.accent_changes2 - Copy.txt
Procedure code is attached.
What error is displayed in the following experiment?
EXECUTE im_automation.accent_changes
WITH RESULT SETS
(
(
[Source] VARCHAR(30),
Category VARCHAR(30),
. . . and so on . . .
),
(
x int
)
)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 86%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHV%3C/text%3E%3C/svg%3E)
Hi @Naomi Nosonovsky ,
The error is already said it all: the procedure sends one or more additional result sets before or after that final SELECT. You can verify this by run the line EXEC im_automation.accent_changes; in SSMS.
I suspect SET STATISTICS IO ON and SET STATISTICS TIME ON might send information as additional result sets. Please try remove it.
Also try verifying all the SELECT statements you use in the query to make sure there is only one result sets in the final SELECT.
Could the RAISERROR messages be considered as extra result sets?
Looks like SET STATISTICS commands were indeed the culprit.