Comments on: The XML Source component – The Basics http://www.bimonkey.com/2009/04/the-xml-source-component-the-basics/ James Beresford on Microsoft BI and Consulting in Sydney, Australia Mon, 06 Feb 2012 16:00:48 +0000 hourly 1 http://wordpress.org/?v= By: BI Monkey http://www.bimonkey.com/2009/04/the-xml-source-component-the-basics/comment-page-1/#comment-1907 BI Monkey Sun, 06 Jun 2010 11:45:09 +0000 http://www.bimonkey.com/?p=112#comment-1907 You can do this from the Control Flow. If you check the properties of the Data Flow containing the XML Source, you will see this property: [XMLSource].[XMLData]. You can set this via an Expression. It's a bit ugly but it works. The same trick applies to any data source, so it can be useful for feeding dynamic queries into OLE DB & ADO.NET sources that don't support parameterised queries. You can do this from the Control Flow. If you check the properties of the Data Flow containing the XML Source, you will see this property: [XMLSource].[XMLData]. You can set this via an Expression.

It’s a bit ugly but it works. The same trick applies to any data source, so it can be useful for feeding dynamic queries into OLE DB & ADO.NET sources that don’t support parameterised queries.

]]> By: Chris http://www.bimonkey.com/2009/04/the-xml-source-component-the-basics/comment-page-1/#comment-1900 Chris Sat, 05 Jun 2010 00:42:51 +0000 http://www.bimonkey.com/?p=112#comment-1900 Hi there, How do I use a variable for the XSD location as I don't know where the file will be installed at the client site and I need to put this location into a configuration table in the database. Cheers. Hi there, How do I use a variable for the XSD location as I don’t know where the file will be installed at the client site and I need to put this location into a configuration table in the database. Cheers.

]]> By: BI Monkey http://www.bimonkey.com/2009/04/the-xml-source-component-the-basics/comment-page-1/#comment-727 BI Monkey Sun, 06 Dec 2009 02:16:45 +0000 http://www.bimonkey.com/?p=112#comment-727 I would suspect that you have an incorrect XSD file - this is what translates the data from the XML. Nested elements can be a pain to work with. Visual Studio has probably generated something that doesn't quite work - look at the XSD definition documentation - it's patchy but should get you on teh right track. I would suspect that you have an incorrect XSD file – this is what translates the data from the XML. Nested elements can be a pain to work with. Visual Studio has probably generated something that doesn’t quite work – look at the XSD definition documentation – it’s patchy but should get you on teh right track.

]]> By: Tammy http://www.bimonkey.com/2009/04/the-xml-source-component-the-basics/comment-page-1/#comment-721 Tammy Thu, 03 Dec 2009 12:51:31 +0000 http://www.bimonkey.com/?p=112#comment-721 I'm currently trying to load an xml file into a temp table I've created. When I create the connection I have "three" XML categories (Organization, People, Place). I get External Columns for Organization and Place that I can then select to populate my temp table, but my People shows just one column and I can't figure out why. When I look at the XML file the People element has sub elements and they are populated with data. I'm not sure if it's a bug in VS 2005, a bug in SSIS, and incorrect Schema file generated by VS 2005, a poorly generated XML.doc file generated by a SOAP, or some other issue I haven't thought of. Any ideas? I'm not an XML person and if I had my choice I wouldn't have picked XML as the file type but alas you work with what you get. Thanks in advance for the help provided. I’m currently trying to load an xml file into a temp table I’ve created. When I create the connection I have “three” XML categories (Organization, People, Place). I get External Columns for Organization and Place that I can then select to populate my temp table, but my People shows just one column and I can’t figure out why. When I look at the XML file the People element has sub elements and they are populated with data. I’m not sure if it’s a bug in VS 2005, a bug in SSIS, and incorrect Schema file generated by VS 2005, a poorly generated XML.doc file generated by a SOAP, or some other issue I haven’t thought of. Any ideas? I’m not an XML person and if I had my choice I wouldn’t have picked XML as the file type but alas you work with what you get. Thanks in advance for the help provided.

]]> By: BI Monkey http://www.bimonkey.com/2009/04/the-xml-source-component-the-basics/comment-page-1/#comment-523 BI Monkey Tue, 27 Oct 2009 10:20:24 +0000 http://www.bimonkey.com/?p=112#comment-523 Most likely your XSD isn't quite right if no data is going through the pipeline. The XSD provides something the XML source can read and translate into columns. If the data doesn't conform to what is described in the XSD it is quite possible for the process to silently "fail" as it cannot recognise any data to pass on. Consider testing your XSD with the SQL Server XML Bulk Loader, i've done a post on it here in the past. Most likely your XSD isn’t quite right if no data is going through the pipeline. The XSD provides something the XML source can read and translate into columns. If the data doesn’t conform to what is described in the XSD it is quite possible for the process to silently “fail” as it cannot recognise any data to pass on.

Consider testing your XSD with the SQL Server XML Bulk Loader, i’ve done a post on it here in the past.

]]> By: Andrew http://www.bimonkey.com/2009/04/the-xml-source-component-the-basics/comment-page-1/#comment-497 Andrew Mon, 19 Oct 2009 14:39:05 +0000 http://www.bimonkey.com/?p=112#comment-497 I'm trying to pull in soap messages using the XML source in SSIS 2005. I wrote an XSD that breaks down the elements. When I point the XML source to the XML file and XSD it shows me the columns correctly. I then map these to an OLE DB Destination. At this point everything is setup with no warnings or errors. The package then executes sucessfully, however, there is no data in the desintation table. Any thoughts on what might be causing this? I’m trying to pull in soap messages using the XML source in SSIS 2005. I wrote an XSD that breaks down the elements. When I point the XML source to the XML file and XSD it shows me the columns correctly. I then map these to an OLE DB Destination. At this point everything is setup with no warnings or errors.

The package then executes sucessfully, however, there is no data in the desintation table. Any thoughts on what might be causing this?

]]> By: BI Monkey http://www.bimonkey.com/2009/04/the-xml-source-component-the-basics/comment-page-1/#comment-176 BI Monkey Tue, 18 Aug 2009 07:35:22 +0000 http://www.bimonkey.com/?p=112#comment-176 Hi Leigh - the response in the forum is probably in line with what I would suggest - the Advanced Editor is about your best bet, but if Elements are changing name the GUI for the component may simply be unable to cope. However that doesn't mean you are out of luck - if you look at the raw XML of the package (View > Code in Visual Studio) - you can probably edit the xml describing the inputs that have changed name and bypass the GUI altogether. It's ugly - backup first - but may well save you having to remap everything. Let me know how you get on. Oddly enough i've been wrestling with XML quite a bit for the last day or two, it's an evil thing! Hi Leigh – the response in the forum is probably in line with what I would suggest – the Advanced Editor is about your best bet, but if Elements are changing name the GUI for the component may simply be unable to cope.

However that doesn’t mean you are out of luck – if you look at the raw XML of the package (View > Code in Visual Studio) – you can probably edit the xml describing the inputs that have changed name and bypass the GUI altogether. It’s ugly – backup first – but may well save you having to remap everything.

Let me know how you get on. Oddly enough i’ve been wrestling with XML quite a bit for the last day or two, it’s an evil thing!

]]> By: Leigh http://www.bimonkey.com/2009/04/the-xml-source-component-the-basics/comment-page-1/#comment-171 Leigh Mon, 17 Aug 2009 00:42:14 +0000 http://www.bimonkey.com/?p=112#comment-171 How do you deal with minor changes to the Schema without refreshing to whole schema (which breaks everything downstream) ? This is causing me a lot of grief (see my MSDN post): http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/8e39a925-dac2-4647-99b3-338c2b45ceac How do you deal with minor changes to the Schema without refreshing to whole schema (which breaks everything downstream) ? This is causing me a lot of grief (see my MSDN post):

http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/8e39a925-dac2-4647-99b3-338c2b45ceac

]]>