Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
· The US census uses the Soundex system to catalog names for proximity searching. An explanantion of the principles of the algorithm can be found here: [http://www.archives.gov/research/census/soundex.html]
1.) Direct SQL is classified as a dangerous API and requires code-access-security assertion on the server. This often causes ISV’s problems with Microsoft software certification.
2.) It will limit the soundex-codes to the language that SQL Server was installed in (US-EN). Enhancing the algorithm below (manually) will allow you to tailor language specific pronounciation.
· The result of the above should be a soundex code of (F260) for both.
· Again, these noise-words are language specific and the ultimate solution needs to cater for language variants.
· (Global and targeted searches for similar sounding words).
· Bulk populate (clear down, re-calculate, re-populate) the entire soundex word index using X++.
· Same as above using a SQL agent or SSIS job.
· Iterative updates using “post-event handlers” (either X++ or .Net)
· Note, when populating Dynamics tables using this approach you must ensure that they will only ever be used as lookup/reference tables. It really doesn’t matter what you put into the RecId column, just so long its unique.
This is really impressive stuff! Thank you for sharing. :D