<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SQL SERVER &#8211; Solution to Puzzle &#8211; Shortest Code to Perform SSN Validation</title>
	<atom:link href="http://blog.sqlauthority.com/2009/04/29/sql-server-solution-to-puzzle-shortest-code-to-perform-ssn-validation/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2009/04/29/sql-server-solution-to-puzzle-shortest-code-to-perform-ssn-validation/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Fri, 10 Feb 2012 04:35:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Tore Bostrup</title>
		<link>http://blog.sqlauthority.com/2009/04/29/sql-server-solution-to-puzzle-shortest-code-to-perform-ssn-validation/#comment-130032</link>
		<dc:creator><![CDATA[Tore Bostrup]]></dc:creator>
		<pubDate>Tue, 19 Apr 2011 20:01:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=4647#comment-130032</guid>
		<description><![CDATA[For those who plan to use this in an actual system, it is important to research the issue in more depth.  Specifically know that:
1:  The &quot;Area Number&quot; list is only one part of the validation, the two digit Group Number is also assigned in a particular order (using a peculiar odd/even group number assignment sequence, see http://www.socialsecurity.gov/history/ssn/geocard.html).  The last group number in use is published monthly (http://www.socialsecurity.gov/employer/ssnvhighgroup.htm).
2:  On June 25, 2011, all this will change as SSN randomization will be introduced (or at least that is the plan at this time - http://www.socialsecurity.gov/employer/randomizationfaqs.html).  The Area Number/Group Number still applies to SSNs issued prior to that time, but new SSNs will not follow that pattern.
3:  For serious SSN verification, one should also consider the Social Security Administration&#039;s Death Master File, containing over 65 million thus &quot;expired&quot; SSNs.]]></description>
		<content:encoded><![CDATA[<p>For those who plan to use this in an actual system, it is important to research the issue in more depth.  Specifically know that:<br />
1:  The &#8220;Area Number&#8221; list is only one part of the validation, the two digit Group Number is also assigned in a particular order (using a peculiar odd/even group number assignment sequence, see <a href="http://www.socialsecurity.gov/history/ssn/geocard.html" rel="nofollow">http://www.socialsecurity.gov/history/ssn/geocard.html</a>).  The last group number in use is published monthly (<a href="http://www.socialsecurity.gov/employer/ssnvhighgroup.htm" rel="nofollow">http://www.socialsecurity.gov/employer/ssnvhighgroup.htm</a>).<br />
2:  On June 25, 2011, all this will change as SSN randomization will be introduced (or at least that is the plan at this time &#8211; <a href="http://www.socialsecurity.gov/employer/randomizationfaqs.html" rel="nofollow">http://www.socialsecurity.gov/employer/randomizationfaqs.html</a>).  The Area Number/Group Number still applies to SSNs issued prior to that time, but new SSNs will not follow that pattern.<br />
3:  For serious SSN verification, one should also consider the Social Security Administration&#8217;s Death Master File, containing over 65 million thus &#8220;expired&#8221; SSNs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pinaldave</title>
		<link>http://blog.sqlauthority.com/2009/04/29/sql-server-solution-to-puzzle-shortest-code-to-perform-ssn-validation/#comment-51395</link>
		<dc:creator><![CDATA[pinaldave]]></dc:creator>
		<pubDate>Wed, 29 Apr 2009 16:21:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=4647#comment-51395</guid>
		<description><![CDATA[Pacer Dawn 
Good observation. I like the way you think.]]></description>
		<content:encoded><![CDATA[<p>Pacer Dawn<br />
Good observation. I like the way you think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pacer Dawn</title>
		<link>http://blog.sqlauthority.com/2009/04/29/sql-server-solution-to-puzzle-shortest-code-to-perform-ssn-validation/#comment-51394</link>
		<dc:creator><![CDATA[Pacer Dawn]]></dc:creator>
		<pubDate>Wed, 29 Apr 2009 15:53:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=4647#comment-51394</guid>
		<description><![CDATA[AND A  &#039;666&#039; AND B &gt; &#039;00&#039; AND C &gt; &#039;0000&#039;
AND ssn NOT LIKE &#039;%[^0-9-]%&#039;

There is no need for the upper bound check as we have already verified B and C are exactly 2 and 4 digits respectively.  We also need to verify there are no non-digits (other than dashes) in there. 

Also, is &quot;DISTINCT&quot; necessary?  I don&#039;t see anywhere in the rules where it has to be a unique list, and that does add characters to the final SQL.]]></description>
		<content:encoded><![CDATA[<p>AND A  &#8217;666&#8242; AND B &gt; &#8217;00&#8242; AND C &gt; &#8217;0000&#8242;<br />
AND ssn NOT LIKE &#8216;%[^0-9-]%&#8217;</p>
<p>There is no need for the upper bound check as we have already verified B and C are exactly 2 and 4 digits respectively.  We also need to verify there are no non-digits (other than dashes) in there. </p>
<p>Also, is &#8220;DISTINCT&#8221; necessary?  I don&#8217;t see anywhere in the rules where it has to be a unique list, and that does add characters to the final SQL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kurt Koller</title>
		<link>http://blog.sqlauthority.com/2009/04/29/sql-server-solution-to-puzzle-shortest-code-to-perform-ssn-validation/#comment-51376</link>
		<dc:creator><![CDATA[Kurt Koller]]></dc:creator>
		<pubDate>Wed, 29 Apr 2009 03:13:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=4647#comment-51376</guid>
		<description><![CDATA[I&#039;m reading this from my phone but how&#039;s that code work for:

214-2n-9999
21g-55-9999
2g3-44-9999

Etc]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m reading this from my phone but how&#8217;s that code work for:</p>
<p>214-2n-9999<br />
21g-55-9999<br />
2g3-44-9999</p>
<p>Etc</p>
]]></content:encoded>
	</item>
</channel>
</rss>

