-- SAMPLE TABLE

DECLARE @t TABLE (

error_reference_uid VARCHAR(10),

item_number VARCHAR(10),

error_code VARCHAR(10) )

-- SAMPLE DATA

INSERT INTO @t (error_reference_uid,item_number,error_code) SELECT '1234567','13579','odd'

INSERT INTO @t (error_reference_uid,item_number,error_code) SELECT '1234567','2468','even'

INSERT INTO @t (error_reference_uid,item_number,error_code) SELECT '1234568','13579','odd'

INSERT INTO @t...

If you need to join with the results of OPENXML in more than one query/batch, it is advisable to put the results of OPENXML into a memory/temp table and use...

this must be a limitation on displaying the text at SSMS. refer this article http://www.sqlservercentral.com/articles/XML/62054/ that shows how to retrieve XML results with ADO.NET

I dont think FOR XML will give you better performance. FOR XML may not be used as a means to increase performance. It is usually used when an XML output...

Agreed.

Try this

;WITH cte AS (

SELECT

name,

count(*) OVER (PARTITION BY '') cnt,

ROW_NUMBER() OVER (ORDER BY name) AS recID

FROM sys.tables

)

SELECT name, RecID, cnt

FROM cte WHERE RecID BETWEEN 5 AND 10

Did you try the "COUNT(*) OVER(PARTITION BY '')" option suggested by Matt, earlier in this thread? This will give you the recordcount.

Hi Paul,

Thank you for the feedback. The code was just for the purpose of demonstration only. My focus was on getting the FOR XML results to the .NET application into...

Hi Phil,

Thank you for bringing this up. I had plans to cover SQLXML in the later sessions. On the .NET part, i was pretty sure that I could be missing...

I see that the editor has deleted XML tags in my post. So the XQUERY that you asked me in the previous post should look like this: (i am replacing...

aplogies for the bad formatting. the editor does not help me to format correctly. I must be missing something. And my xml data is also missing in the post. But...

Are you looking for something like the following?

DECLARE @x XML

SET @x =

'

...

You could do this by using a variable. You can refer to an element/attribute as 'sql:variable("@varname")'. Look for sql:variable in books online. I have covered this in "XML Workshop...

Thanks everyone for the interesting feed back. I agree that FOR XML PATH is much easier and almost as power ful as EXPLICIT. I also agree that the process of...

I agree that sp_executesql is better than EXEC() in many ways. Other than reusing the execution plan, it helps to avoid SQL Injection. I have mentioned it in one of...