XML xsi:noNamespaceSchemaLocation

I am trying to use a stored procedure in SQL Server 2005 to create a xml file for a document management system.  The code I am using is:

WITH XMLNAMESPACES (
'\\SomeServer\SomeFile\Some.xsd'
as noNamespaceSchemaLocation,
'http://www.w3.org/2001/XMLSchema-instance' as xsi
)

Select 'Some SQL Code '

FOR XML PATH ('Path'), ELEMENTS, TYPE, ROOT('Root')

The Results I get are:
<Root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:noNamespaceSchemaLocation="\\SomeServer\SomeFile\Some.xsd">
  <Path>Some SQL Code </Path>
</Root>

The Results I would like to get are:
<Root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="\\SomeServer\SomeFile\Some.xsd">
  <Path>Some SQL Code </Path>
</Root>

Basically, I need the xmlns:noNamespaceSchemaLocation to be xsi:noNamespaceSchemaLocation

I am new to the XML world so any assistance would be appreciated.

Thanks.

-JAllen

jallen_gomedicoAsked:
Who is Participating?
 
Mark WillsTopic AdvisorCommented:
Nope... Even when specifically telling it to with the XSINIL declaration...

From BOL : The XML namespace prefix xsi cannot be redeclared when the ELEMENTS XSINIL directive is being used on the query.

But there are some "tricks" depending on how complex your query really is...


WITH XMLNAMESPACES ('http://www.w3.org/2001/XMLSchema-instance' AS xsi)
SELECT '\\SomeServer\SomeFile\Some.xsd' "@xsi:noNamespaceSchemaLocation",  
  'Some SQL Code' AS Path
FOR XML PATH('Root'), ELEMENTS XSINIL
;


0
 
Kevin CrossChief Technology OfficerCommented:
jallen_gomedico,

xmlns: is what appears before all namespace prefixes; therefore, if you are wanting a namespace prefix of noNamespaceSchemaLocation then xmlns: should proceed it and not xsi.

http://www.w3schools.com/xml/xml_namespaces.asp

Please clarify what your intent is, so can figure out if I am missing your point here.  Otherwise, you could want to specify namespace for elements that don't have a prefix and that would be xmlns with no :{prefix} after it.
0
 
Kevin CrossChief Technology OfficerCommented:
This might be a better reference for you as it is the BOL from Microsoft specifically regarding SQL's WITH XMLNAMESPACES versus the other was just to exemplify for you how xmlns is used.

http://msdn.microsoft.com/en-us/library/ms177400.aspx
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
jallen_gomedicoAuthor Commented:
mwvisa1,

Thanks for the reponses.  Although the links help in the understanding of the namespaces, they didn't really help with my issue.  I see plenty of examples on various forums of xml with xsi:noNamespaceSchemaLocation but I would like to see some sql on how this is acheived...

Thanks.

-JAllen
0
 
Kevin CrossChief Technology OfficerCommented:
Yeah, I believe I know what you are trying to do, but don't believe that is possible with xmlnamepaces; however, I will call some other experts in SQL to see if they know how to work around this.

0
 
jallen_gomedicoAuthor Commented:
Thanks!
0
 
Kevin CrossChief Technology OfficerCommented:
Thanks for joining in, Mark!
0
 
jallen_gomedicoAuthor Commented:
Thanks Mark, and you too mwvisa1!

0
 
Mark WillsTopic AdvisorCommented:
No problems, and thanks to mwvisa1 for getting in touch :)

Just as a small "bonus" for more complex queries you can resort to something like (usinf dynamic SQL so you can more easily construct the list of elements):

declare @my_xml_insert nvarchar(max)

set @my_xml_insert = '
DECLARE @myXML XML
set @myXML = ''<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="\\SomeServer\SomeFile\Some.xsd">
   <PATH> </PATH>
</root>''

'
set @my_xml_insert = @my_xml_insert + 'SET @myXML.modify(''          
insert (          
    <Element1>1</Element1>,          
    <Element2>3</Element2>          
   )          
into (/root/PATH)[1] '')

select @myXML'

exec (@my_xml_insert)          

-- and in 2008 then you can list those added elements by using the insert sql:variable construct and get rid of the dynamic sql :

-- First we need to build an appropriate variable to use for the insert, so, @newelements is something like :

DECLARE @newElements xml
set @newelements = (select ProductID,name,productnumber from production.product for xml path('Product'))

DECLARE @myXML XML
set @myXML = '<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="\\SomeServer\SomeFile\Some.xsd">
   <PATH> </PATH>
</root>'

SET @myXML.modify('insert sql:variable("@newElements") into (/root/PATH)[1]')

-- hope that helps just a bit more...  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.