Hi,

You can achieve this by using a predicate to target the attributes, here is something that will hopefully get you on the right track:

DECLARE @xml XML =...

• This reply was modified 2 years, 3 months ago by  Arthur Olcot. Reason: typo in column name

Hi, what you could do is to use a second cross apply within the same query to join on the other data. I've also tweaked the query to use the...

No problem.. thanks for the feedback 🙂

I've just run your query, using a temp table of the same name + example xml, and it works fine.

CREATE TABLE #xNESP_XmlImportPOData (xml_data XML)

INSERT INTO #xNESP_XmlImportPOData (xml_data)

VALUES ('<message>

...

ok. i just did a quick google and there were a number of free online xsd from xml generators on the first page. not tried any myself so can't comment...

You can use visual studio to create a schema from an xml document, and generally it will...

One option that I often use for ad-hoc imports of XML if you can get the xml files onto the SQL server is this method:

declare @xml xml

SELECT @xml = BulkColumn...

No problem, thanks for the feedback.. Happy new year to you too.

Hi, glad you got to the bottom of it!.

I think I understand what you are trying to do i.e. show the fragmentation as a percentage i.e. 85.5%? If so then...

Hi. At face value, the xpath is correct for the xml example that you have posted so at this point I'd go and do some sanity checks on the base...

BWFC (12/11/2014)

The answer might be in the title, but as a newbie I went through my usual process of reading the question,...

Here is a slightly different take on the suggestion by Eirikur that achieves the same but without querying the system views. I've also opted to use dynamic sql to generate...

Here is another method which gets the NomProcess node immediately following the IdProcess node of the value that you specify

DECLARE @xml XML

SET @xml = '<Status>

<IdStatus>1</IdStatus>

<NomStatus>Status 1</NomStatus>

<IdStatus>2</IdStatus>

<NomStatus>Status 2</NomStatus>

<IdStatus>3</IdStatus>

<NomStatus>Status 3</NomStatus>

</Status>

<Process>

<IdProcess>3</IdProcess>

<NomProcess>Process 3</NomProcess>

<IdProcess>2</IdProcess>

<NomProcess>Process...

I know that this thread is a week old and Eirikur has already provided a potential solution but I'd thought I'd add some comments + another solution as well. Firstly...

Hi, you can do it by using a namespace. Here is a not so elegant way of getting the value out:

DECLARE @xml XML = '<?xml version="1.0" encoding="utf-8"?>

<DataSet xmlns="http://tempuri.org/">

<xs:schema id="NewDataSet"...