<?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>T-SQL Tuesday #19: Blind Spots</title><link>http://sqlblog.com/blogs/merrill_aldrich/archive/2011/06/13/t-sql-tuesday-19-blind-spots.aspx</link><description>A while ago I wrote a post, Visualize Disaster , prompted by a real incident we had at my office. Fortunately we came through it OK from a business point of view, but I took away an important lesson: it’s very easy, whether your organization and your</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: T-SQL Tuesday #19: Blind Spots</title><link>http://sqlblog.com/blogs/merrill_aldrich/archive/2011/06/13/t-sql-tuesday-19-blind-spots.aspx#36230</link><pubDate>Tue, 14 Jun 2011 16:26:22 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:36230</guid><dc:creator>merrillaldrich</dc:creator><description>&lt;p&gt;Thanks to Allen Kinsel for hosting this month's T-SQL Tuesday &amp;gt; &lt;a rel="nofollow" target="_new" href="http://www.allenkinsel.com/archive/2011/06/invitation-for-t-sql-tuesday-19-disasters-recovery/"&gt;http://www.allenkinsel.com/archive/2011/06/invitation-for-t-sql-tuesday-19-disasters-recovery/&lt;/a&gt; &lt;/p&gt;
</description></item></channel></rss>