<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www2.sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Adam Machanic : xml</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/xml/default.aspx</link><description>Tags: xml</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>T-SQL Tuesday #002: Is it XML, or Not?!?</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/2010/01/12/t-sql-tuesday-002-is-it-xml-or-not.aspx</link><pubDate>Tue, 12 Jan 2010 21:19:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:20965</guid><dc:creator>Adam Machanic</dc:creator><slash:comments>8</slash:comments><comments>http://www2.sqlblog.com/blogs/adam_machanic/comments/20965.aspx</comments><wfw:commentRss>http://www2.sqlblog.com/blogs/adam_machanic/commentrss.aspx?PostID=20965</wfw:commentRss><description>The query optimizer is a finicky thing , and sometimes it doesn't understand exactly what you're trying to do until you give it a bit more information. The situation I'm going to describe in this post is one such case. By providing the optimizer with...(&lt;a href="http://www2.sqlblog.com/blogs/adam_machanic/archive/2010/01/12/t-sql-tuesday-002-is-it-xml-or-not.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www2.sqlblog.com/aggbug.aspx?PostID=20965" width="1" height="1"&gt;</description><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/_2300_tsql2sday/default.aspx">#tsql2sday</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/puzzle/default.aspx">puzzle</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/T-SQL+Tuesday/default.aspx">T-SQL Tuesday</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/xml/default.aspx">xml</category></item><item><title>Uniquely Identifying XML Nodes with DENSE_RANK</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/2009/08/03/uniquely-identifying-xml-nodes-with-dense-rank.aspx</link><pubDate>Mon, 03 Aug 2009 12:43:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:15704</guid><dc:creator>Adam Machanic</dc:creator><slash:comments>7</slash:comments><comments>http://www2.sqlblog.com/blogs/adam_machanic/comments/15704.aspx</comments><wfw:commentRss>http://www2.sqlblog.com/blogs/adam_machanic/commentrss.aspx?PostID=15704</wfw:commentRss><description>When working with XML in SQL Server, you might want to uniquely identify one node against another. But due to the flexibility with which XML can be defined, this is not always directly possible. SQL Server's own XML structures are guilty of having this...(&lt;a href="http://www2.sqlblog.com/blogs/adam_machanic/archive/2009/08/03/uniquely-identifying-xml-nodes-with-dense-rank.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www2.sqlblog.com/aggbug.aspx?PostID=15704" width="1" height="1"&gt;</description><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/dense_5F00_rank/default.aspx">dense_rank</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/xml/default.aspx">xml</category></item><item><title>Introducing: Extended Events Code Generator v1.0</title><link>http://www2.sqlblog.com/blogs/adam_machanic/archive/2009/07/30/introducing-extended-events-code-generator-v1-0.aspx</link><pubDate>Thu, 30 Jul 2009 19:16:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:15621</guid><dc:creator>Adam Machanic</dc:creator><slash:comments>5</slash:comments><comments>http://www2.sqlblog.com/blogs/adam_machanic/comments/15621.aspx</comments><wfw:commentRss>http://www2.sqlblog.com/blogs/adam_machanic/commentrss.aspx?PostID=15621</wfw:commentRss><description>SQL Server 2008 Extended Events. It's a high-performance, feature-rich, and extremely useful tracing system. Too bad it's so difficult to figure out how to use it ! Or is it? Earlier this week Jonathan Kehayias announced his SSMS addin for Extended Events...(&lt;a href="http://www2.sqlblog.com/blogs/adam_machanic/archive/2009/07/30/introducing-extended-events-code-generator-v1-0.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www2.sqlblog.com/aggbug.aspx?PostID=15621" width="1" height="1"&gt;</description><enclosure url="http://www2.sqlblog.com/blogs/adam_machanic/attachment/15621.ashx" length="6756" type="application/zip" /><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/code+generator/default.aspx">code generator</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/extended+events/default.aspx">extended events</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/Performance/default.aspx">Performance</category><category domain="http://www2.sqlblog.com/blogs/adam_machanic/archive/tags/xml/default.aspx">xml</category></item></channel></rss>