<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://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>My SQLBits Pre Conference Seminar - SSDT Database projects from the ground-up</title><link>http://sqlblog.com/blogs/jamie_thomson/archive/2013/01/15/my-sqlbits-pre-conference-seminar-ssdt-database-projects-from-the-ground-up.aspx</link><description>Over the last year or so it will not have escaped my regular readers’ attention that much of my blogging has centred around SSDT database projects . SSDT (and its variously named forebears) is a tool that I have been using in some way, shape or form since</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>Continuous deployment of SSDT database projects to Windows Azure using Team Foundation Service</title><link>http://sqlblog.com/blogs/jamie_thomson/archive/2013/01/15/my-sqlbits-pre-conference-seminar-ssdt-database-projects-from-the-ground-up.aspx#47340</link><pubDate>Sun, 27 Jan 2013 20:07:29 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:47340</guid><dc:creator>SSIS Junkie</dc:creator><description>&lt;p&gt;Continuous deployment is described by Wikipedia as: Most CI systems allow the running of scripts after&lt;/p&gt;
</description></item></channel></rss>