Simple XML .query SELECT statement times out on 1 SQL SERVER instance I dropped and recreated a stored procedure on a DB on a SQL Server 2012 instance (SERVER1/INSTANCE1), after which the sproc started hanging on a line.   Using profiler I have reduced a recreateable scenario on this SQL Server instance to the following code:

DECLARE @RequestXML xml = '&lt;Foo&gt;
    &lt;Node1&gt;Hello&lt;/Node1&gt;
    &lt;Node2&gt;World&lt;/Node2&gt;
    &lt;Node3&gt;Today&lt;/Node3&gt;
&lt;/Foo&gt;'

SELECT
    @RequestXML.query('/Foo/Node1[1]')
    ,@RequestXML.query('/Foo/Node2[1]')
    ,@RequestXML.query('/Foo/Node3[1]') -- comment out any of these lines so only one or two items are returned and the query works fine!


This statement hangs.   If you comment out one of the returned columns in the SELECT statement, then the statement runs fine.  So one of two returned columns is fine, but anything over is bad.  If you take out the first node selector (i.e. the [1]) it also runs fine.

Here's the rub though:


the statement fails on any DB in this SQL Server 2012 instance (SERVER1/INSTANCE1).
the statement succeeds on any other SQL Server instance I have tried, including  other instances running from the same SQL Server machine as the failing instance (e.g. SERVER1/INSTANCE2, SERVER1/INSTANCE3 etc.) - all of which are 2012 instances.


It seems to me that SERVER1/INSTANCE1 has borked the way it runs this statement.  I have heard that SQL Server does things with optimising execution of statements, but my knowledge stops there.  I'm sure there must be some way to get it to behave again, but how?

UPDATE

The following adjustment (getting the singleton of the Xpath result-set rather than potentially multiple first elements) solves the issue above for the SERVER1/INSTANCE1 issue.  I would put this as the answer, except that I don't believe this is identifying the underyling problem (please correct me if I'm wrong!).  Given that our codebase deployed on other servers implements the above statement (or derivatives of it) I don't want to update our entire shredding XML approach without good reason (or at least I would have to justify it to my peers).

DECLARE @RequestXML xml = '&lt;Foo&gt;
    &lt;Node1&gt;Hello&lt;/Node1&gt;
    &lt;Node2&gt;World&lt;/Node2&gt;
    &lt;Node3&gt;Today&lt;/Node3&gt;
&lt;/Foo&gt;'

SELECT
    @RequestXML.query('(/Foo/Node1)[1]')
    ,@RequestXML.query('(/Foo/Node2)[1]')
    ,@RequestXML.query('(/Foo/Node3)[1]')


Any help gratefully received.

Thanks,

Ali
I'm not sure if it answers your question, but I had a similar problem. The resulution was limiting SQL Server to execute the query using one processor only.

If you have the same problem, this should work:

DECLARE @RequestXML xml = '&lt;Foo&gt;
    &lt;Node1&gt;Hello&lt;/Node1&gt;
    &lt;Node2&gt;World&lt;/Node2&gt;
    &lt;Node3&gt;Today&lt;/Node3&gt;
&lt;/Foo&gt;'

SELECT
    @RequestXML.query('/Foo/Node1[1]')
    ,@RequestXML.query('/Foo/Node2[1]')
    ,@RequestXML.query('/Foo/Node3[1]') 
OPTION(MAXDOP 1)


The thing is that SQL Server Query Optimizer decides that the query is costly enough to split its execution and merge those results. And sometimes this creates problems, so lowering degree of parallelism (MAXDOP) can solve it.

EDIT

Looking at the execution plan for this query, I find it hard to believe that somewhere in the middle of execution of each branch for @RequestXML.query('...'), estimated number of rows was 180,000. However, when I told it that I promise I will need only the first Foo, he reduced it to 900. So, try this...

DECLARE @RequestXML xml = '&lt;Foo&gt;
    &lt;Node1&gt;Hello&lt;/Node1&gt;
    &lt;Node2&gt;World&lt;/Node2&gt;
    &lt;Node3&gt;Today&lt;/Node3&gt;
    &lt;Node4&gt;Tomorrow&lt;/Node4&gt;
&lt;/Foo&gt;'

SELECT
    @RequestXML.query('/Foo[1]/Node1[1]')
    ,@RequestXML.query('/Foo[1]/Node2[1]')
    ,@RequestXML.query('/Foo[1]/Node3[1]')
    ,@RequestXML.query('/Foo[1]/Node4[1]')