[dba-SQLServer] Update query leaves null

Wow! I MUST check into this! Thanks for the heads up! But I think that this can still be done in SQL 2000+ using a calculated column. I shall begin my experiments and let y'all know wha 'appen.

Arthur

----- Original Message ----
From: Jim Lawrence <accessd at shaw.ca>
To: dba-sqlserver at databaseadvisors.com
Sent: Monday, August 14, 2006 1:46:18 PM
Subject: Re: [dba-SQLServer] Update query leaves null

Hi John:

With the latest fuzzy match Soundex algorithm (enhanced version...US census
uses it.) it will translate a field of data into a simplified number. See
http://en.wikipedia.org/wiki/Soundex and
http://www.creativyst.com/Doc/Articles/SoundEx1/SoundEx1.htm for details and
access to code samples. (I have one around here somewhere and will send a
copy when found...)

Example:
Twin Pines Drive, Twin Pines Dr and Twin Pines Dr. would resolve to index
T515 which I believe is what you are looking for.

The Soundex field would have to be created and populated after the 60
million odd rows have been imported... post process. And the address number
will have to be managed; maybe as a separate field.    

Jim