I find that these XML questions are never as easy as they first seem to be.
DECLARE @xml XML
SELECT @xml =
'<row id="VFAL.2312" xml:space="preserve">
<c1>DETAIL</c1>
<c2>VFAL.2312</c2>
<c2 m="2">272101-01</c2>
<c2 m="3">AIR DLG-DOUBTFUL LOAN VB>1Y</c2>
<c90>1</c90>
<c91>43_VFC.2__OFS_BROWSERTC</c91>
<c92>1208061131</c92>
<c93>43_VFC.2_OFS_BROWSERTC</c93>
<c94>KH0010001</c94>
<c95>1</c95>
</row>'
SELECT [@ID]=row.value('@id[1]', 'VARCHAR(10)')
,[Description]=row.value('(./c1)[1]', 'VARCHAR(10)')
FROM (SELECT @xml) a(x) CROSS APPLY x.nodes('row') b(row)
SELECT [@ID]=row.value('(./c2)[1]', 'VARCHAR(10)')
,[Detail Description]
FROM (SELECT @xml) a(x) CROSS APPLY x.nodes('row') b(row)
CROSS APPLY (
VALUES (row.value('(./c2)[2]', 'VARCHAR(10)'))
,(row.value('(./c2)[3]', 'VARCHAR(50)'))) c ([Detail Description])
Probably your actual XML contains additional elements that need to be taken into consideration or other bits of information to be shredded out. But perhaps the above will get you started.
If you've never seen CROSS APPLY VALUES before, take a look here: http://www.sqlservercentral.com/articles/CROSS+APPLY+VALUES+UNPIVOT/91234/
Edit: BTW. I am no expert on XML so if someone out there has a better way to handle this particular example, I (and my fish) are all ears. 🙂
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?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St