<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Testing for Database Null Values from PowerShell</title><link>http://blogs.technet.com/industry_insiders/pages/testing-for-database-null-values-from-powershell.aspx</link><description>PowerShell is super, but its documentation is still lousy. You might think that how to test a database field for a null value would be straightforward, and indeed it is, but it ain’t documented anywhere. I’ve just spent the afternoon searching and eventually</description><dc:language>en-GB</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>All about Nothing- SQL Server Nulls in Powershell</title><link>http://blogs.technet.com/industry_insiders/pages/testing-for-database-null-values-from-powershell.aspx#3124223</link><pubDate>Mon, 15 Sep 2008 11:52:35 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3124223</guid><dc:creator>Andrew Fryer's Blog</dc:creator><description>&lt;p&gt;Finding stuff about one Microsoft technology isn’t too hard it’s when you try and use two things get&lt;/p&gt;
</description></item></channel></rss>