StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11569188
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-07-19T20:58:51.177
FavoriteCount
0
LastActivityDate
2012-07-19T20:58:51.177
LastEditDate
LastEditorUserId
0
OwnerUserId
1539001
ParentId
8211159
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The second of the two articles below shows how to use an XLST file in SSIS to transform the XML source file into something you can use for your described purpose. I provide two XSLT file contents at the bottom. <code>http://sqlserverpedia.com/blog/sql-server-bloggers/loading-xml-using-ssis/</code> <a href="http://blog.hoegaerden.be/2011/04/20/loading-complex-xml-using-ssis/" rel="nofollow">http://blog.hoegaerden.be/2011/04/20/loading-complex-xml-using-ssis/</a> Repairs to listed data sample: 1) Remove the space in what appears to be a comment at the beginning: '...xmldata/1/ xmldata.xsd...' to 'xmldata/1/xmldata.xsd' 2) Add <code></data></dataset></code> to the very end of the data. You can test it here (Hmmmm, it doesn't seem to work there!): <code>http://www.w3schools.com/xsl/tryxslt.asp?xmlfile=cdcatalog&xsltfile=cdcatalog</code> Or add this as the second line of XML to test in IE by opening the XML file: <pre><code><?xml-stylesheet type="text/xsl" href="Cognos.xsl"?> </code></pre> Look over the xslt listings carefully and note the differences in the 'output' element. Note that I needed to define in my XSLT file the namespace that was used in the XML file's 'dataset' element, and give it a name which I can use to prefix references to the nodes defined within 'dataset'. Assume case sensitivity matters everywhere because it probably does. Do some reading on XSLT elements at: <a href="http://www.w3schools.com/xsl/" rel="nofollow">http://www.w3schools.com/xsl/</a> Cognos.xsl to list contents as 'pipe' (vertical bar) delimited file. There will be an empty column at the end - due to the trailing delimiter - which you will need to ignore in your code that uses the file. <pre><code><?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:cog="http://developer.cognos.com/schemas/xmldata/1/"> <xsl:output method="text" encoding="UTF-8" indent="no" omit-xml-declaration="yes" /> <xsl:template match="/"> <xsl:apply-templates select="cog:dataset/cog:metadata/cog:item"> </xsl:apply-templates> <xsl:text>&#13;&#10;</xsl:text> <xsl:apply-templates select="cog:dataset/cog:data/cog:row"> </xsl:apply-templates> </xsl:template> <xsl:template match="cog:dataset/cog:metadata/cog:item"> <xsl:value-of select="@name"/> <xsl:text>|</xsl:text> </xsl:template> <xsl:template match="cog:dataset/cog:data/cog:row"> <xsl:text>&#13;&#10;</xsl:text> <xsl:apply-templates select="./cog:value"> </xsl:apply-templates> </xsl:template> <xsl:template match="cog:dataset/cog:data/cog:row/cog:value"> <xsl:value-of select="."/> <xsl:text>|</xsl:text> </xsl:template> </xsl:stylesheet> </code></pre> Cognos.xsl to list contents as HTML table: <pre><code><?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:cog="http://developer.cognos.com/schemas/xmldata/1/"> <xsl:output method="html" encoding="UTF-8" indent="yes" /> <xsl:template match="/"> <html><body> <table border="1"><tr> <xsl:apply-templates select="cog:dataset/cog:metadata/cog:item"> </xsl:apply-templates> </tr> <xsl:text>&#13;&#10;</xsl:text> <xsl:apply-templates select="cog:dataset/cog:data/cog:row"> </xsl:apply-templates> </table> </body></html> </xsl:template> <xsl:template match="cog:dataset/cog:metadata/cog:item"> <td> <xsl:value-of select="@name"/> </td> </xsl:template> <xsl:template match="cog:dataset/cog:data/cog:row"> <tr> <xsl:apply-templates select="./cog:value"> </xsl:apply-templates> </tr> </xsl:template> <xsl:template match="cog:dataset/cog:data/cog:row/cog:value"> <td> <xsl:choose> <xsl:when test=". !='' and . !=' '"> <xsl:value-of select="." /> </xsl:when> <xsl:when test=". =' '"> <xsl:text>space</xsl:text> </xsl:when> <xsl:otherwise> <xsl:text>null</xsl:text> </xsl:otherwise> </xsl:choose> </td> </xsl:template> </xsl:stylesheet> </code></pre> And, yes, you are all welcome for this concise collection of requirements, fixes, links, and techniques which I have spent nearly 14 hours researching. Maybe I will turn this in to an article.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do I import XML files using an SSIS package?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USB H
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COI should have pointed out that Siva's answer is correct, but maybe not the whole story.
 singulars
 PostPostId
 PO
 UserUserId
 USB H

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.