<?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>Documenting sp_ssiscatalog</title><link>http://www2.sqlblog.com/blogs/jamie_thomson/archive/2012/12/05/documenting-sp-ssiscatalog.aspx</link><description>What is the best way to document an API ? Moreover, what is the best way to document a T-SQL API? Before I try to answer those questions I should explain what I mean by “a T-SQL API”. I think of an API as being a collection of well-defined, known, code</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>sp_ssiscatalog v1.0.2.0 now available for download</title><link>http://www2.sqlblog.com/blogs/jamie_thomson/archive/2012/12/05/documenting-sp-ssiscatalog.aspx#48183</link><pubDate>Mon, 11 Mar 2013 22:51:21 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:48183</guid><dc:creator>SSIS Junkie</dc:creator><description>&lt;p&gt;v1.0.2.0 – what’s in it? Things have been a bit quiet on the sp_ssiscatalog front since I last blogged&lt;/p&gt;
</description></item></channel></rss>