xml input to a SP results in a useless Plan

A developer is using xml to inpput several parameters into this SP. The result is a Plan that only estimates one row will be returned on every statement, when the Actual Execution Plan returns many thousands on some statements in here.

What can I do to have SQL server build a better plan for this? Optimize for unknown trace flag?

I can't ask him to stop using XML input.

I enclose the Plan Explorer saved file, I couldn't sent it from Plan Explorer though, that failed.

[1]: /storage/temp/2100-xmlinput.pesession

avatar image By mauripop 1 asked Oct 10 at 12:15 AM
more ▼
(comments are locked)
10|10000 characters needed characters left

0 answers: sort voted first
Be the first one to answer this question
toggle preview:

Up to 50 attachments (including images) can be used with a maximum of 209.7 MB each and 209.7 MB total.

Follow this question

Topics:

x2
x1
x1
x1

asked: Oct 10 at 12:15 AM

Seen: 4 times

Last Updated: Oct 10 at 12:15 AM