Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
Julie C.
Starting Member
3 Posts |
Posted - 2010-04-27 : 18:10:42
|
For example, we have a customer called Jenny Lucki in our DB already. Then next time she informs us to buy another product by using her name as: Jennifer Lucki. Right now our name matching process is to called a stored procedure using SQL like this:select * from *** where C_LastName LIKE LTRIM(RTRIM(@LastName)) and C_FirstName like LTRIM(RTRIM(@FirstName)) and C_Birthdate = @BirthdateApparently, this approach wont work with my example and our DB suffering from lots of duplicate customer records by this issue. So I'm wondering is there any other way to do customer name matching/address matching? I know we have fuzzy grouping and fuzzy lookup in SSIS, but I dont know whether it's possible to implement such feature as a function so that our transaction system could call it every time when users do searching.TIA,Julie |
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
Julie C.
Starting Member
3 Posts |
Posted - 2010-04-27 : 18:37:37
|
Thanks, Tara, but I'm afraid full-text indexing is not we are looking for. First, It still wont work with name matching like "Jenny" v.s. "Jennifer" since full-text indexing is still using "exact" match inside a word. And it probably will slow down processing time too much since we have tons of customer data in DB. Actually, what we eventually looking for is more flexible matching, such as "#7-3091 Broad Street" v.s. "3091 Broad St. Apt. 7". It sounds a little bit hard but I saw some companies got "perfect" matching system. Im wondering how they implement the process, probably outside of database? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
Julie C.
Starting Member
3 Posts |
Posted - 2010-04-28 : 11:15:21
|
Thank you, I will take a look at~ |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
|