Multiple namespaces in an XML document

Question

I have an XML document that I am trying to use within a data flow (XML Source)--the problem is that I keep getting an error message stating that the XML document has multiple namespaces and therefore, SSIS will not create the XSD for me.  If I take out the second namespace, I am able to successfully get the task to execute, but this XML is created with 2 namespaces and there is no way to get around this (I cannot get the report server to change these parameters)--my question is: does anyone know of a way to get SSIS to handle multiple namespaces so that I can process this XML document and extract the necessary data elements from it.
Any assistance would be greatly appreciated.
Thank you!!!!

Answer 1

I am replying too much late..........thinking might be useful for someone !!!!
SSIS does not handle multiple namespaces in the XML source file. You can find examples where you see the format
<Namespace:Element>.
The first step to avoid multiple namespaces is to transform your source file to a format that doesn’t refer to the namespaces.
SSIS has an XML task that can do the transformation. Add the XML task to an SSIS Control Flow and edit it.
Change the OperationType property value to XSLT, the SourceType to File connection and the Source to your source file that has the problem.
Set the SaveOperationResult property to True.
Expand the OperationResult branch and Set DestinationType to File Connection and the Destination to a new XML file.
Add the following to a new file and save it with an xslt file extension.
<?xml version="1.0" encoding="utf-8" ?> 
<xsl:stylesheet version="1.0"         xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> 
  <xsl:output method="xml" indent="no" /> 
  <xsl:template match="/|comment()|processing-instruction()"> 
    <xsl:copy> 
      <xsl:apply-templates /> 
    </xsl:copy> 
  </xsl:template> 
  <xsl:template match="*"> 
    <xsl:element name="{local-name()}"> 
      <xsl:apply-templates select="@*|node()" /> 
    </xsl:element> 
  </xsl:template> 
  <xsl:template match="@*"> 
    <xsl:attribute name="{local-name()}"> 
      <xsl:value-of select="." /> 
    </xsl:attribute> 
  </xsl:template> 
</xsl:stylesheet> 
Back in the XML task, set the SecondOperandType to File connection and the Second Operand to your new XSLT file.
When you run the XML task, it will take your original file and apply the transformation rules defined in the XSLT file. The results will be saved in your new XML file.
This task only needs to be run once for the original XML file. When you look at the new file, you’ll see the same data as in the original, but without namespace references.
Now you can return to your data flow and alter the XML Source to reference the new XML file.
Click on the Generate XSD and you should be able to avoid your error.
When you click on the Columns tab in your XML Source, you will probably see a warning. This is because the data types may not be fully defined (for example there’s no mention of string lengths). This shouldn’t be a problem as long as the default data type
(255-character Unicode string) meets your needs.
=================life is beatiful..so !!===========
       Rahul Vairagi
=================================== Rahul Vairagi =================================== My Blogs: www.sqlserver2005forum.blogspot.com www.knwhub.blogspot.com