﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 7,2000 / T-SQL  / Match firstname lastname / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 22 May 2013 16:06:52 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Match firstname lastname</title><link>http://www.sqlservercentral.com/Forums/Topic14416-8-1.aspx</link><description>[quote][b]Jeff Moden (9/24/2012)[/b][hr][quote][b]emoore 99634 (9/24/2012)[/b][hr]True, but others reading through a forum might be looking for ideas on how to tackle problems like this.[/quote]+1[/quote]+2So I will chime in that I too have been handed this same problem many times over the years and it's a nightmare! The permutations of names that can be entered into a single string value is almost impossible to deal with. (The same issue can occur with addresses...oh my!) Any specific solution would be dependent on the business requirements. The only permanent solution I've found is to parse the name-string into the proper individual columns for prefix, first name, middle name, last name, suffix etc. But this is hard to do for compound names such as 'Van Dyke' or a suffix like 'DDS MD'. For me its always been a laborious iterative process to get the names right. If new data is constantly coming in then this may be difficult to keep up with.Otherwise, one way to deal with searching or filtering on such bastard data (besides the simple LIKE statement) is to set up a Full-Text index on the column and develop the search criteria to use that. This will likely create a lot of false positives and for any large amount of data the best one can usually do is to offer up a list of the closest matches and then let a user pick from the list. When dealing with fuzzy data humans can still do some things much more reliably than our computers.</description><pubDate>Tue, 25 Sep 2012 10:28:58 GMT</pubDate><dc:creator>Steven Willis</dc:creator></item><item><title>RE: Match firstname lastname</title><link>http://www.sqlservercentral.com/Forums/Topic14416-8-1.aspx</link><description>[quote][b]emoore 99634 (9/24/2012)[/b][hr]True, but others reading through a forum might be looking for ideas on how to tackle problems like this.[/quote]+1</description><pubDate>Mon, 24 Sep 2012 14:14:52 GMT</pubDate><dc:creator>Jeff Moden</dc:creator></item><item><title>RE: Match firstname lastname</title><link>http://www.sqlservercentral.com/Forums/Topic14416-8-1.aspx</link><description>True, but others reading through a forum might be looking for ideas on how to tackle problems like this.</description><pubDate>Mon, 24 Sep 2012 08:57:55 GMT</pubDate><dc:creator>emoore 99634</dc:creator></item><item><title>RE: Match firstname lastname</title><link>http://www.sqlservercentral.com/Forums/Topic14416-8-1.aspx</link><description>I don't think the OP will notice because he hasn't logged in since 2009....</description><pubDate>Mon, 24 Sep 2012 07:30:12 GMT</pubDate><dc:creator>laurie-789651</dc:creator></item><item><title>RE: Match firstname lastname</title><link>http://www.sqlservercentral.com/Forums/Topic14416-8-1.aspx</link><description>I would use Fuzzy Matching in SSIS.   Throw everything to temp table.  Remove your direct matches and then fuzzy matching the rest.  Sorry can't give more details, but I did this in a project once when we were trying to correlate various school lists across government agencies.   A joy that was.</description><pubDate>Mon, 24 Sep 2012 07:13:31 GMT</pubDate><dc:creator>emoore 99634</dc:creator></item><item><title>RE: Match firstname lastname</title><link>http://www.sqlservercentral.com/Forums/Topic14416-8-1.aspx</link><description>All valid points. I have done a link to the QAS package we use, (ACE in the USA) which narrows it down. I guess that considering it's not the brightest of requests I have had from Customer Services I will send the extract to them to wade through. Revenge is sweet. &lt;img src=icon_smile_big.gif border=0 align=middle&gt;Thanks for the help! </description><pubDate>Wed, 23 Jul 2003 05:47:00 GMT</pubDate><dc:creator>diesel</dc:creator></item><item><title>RE: Match firstname lastname</title><link>http://www.sqlservercentral.com/Forums/Topic14416-8-1.aspx</link><description>How are you going to cater for Rob, Bob, Robert, Robin, Bert.  They could all be the same person or they could be all different.Speaking as someone who has done more name and address matching than I've had hot dinners this is not something you should do on financially sensitive data such as bank accounts.The best you could hope for would be and exact name and address match, but that is likely to be about 40% of cases if you are lucky. </description><pubDate>Wed, 23 Jul 2003 02:16:00 GMT</pubDate><dc:creator>David.Poole</dc:creator></item><item><title>RE: Match firstname lastname</title><link>http://www.sqlservercentral.com/Forums/Topic14416-8-1.aspx</link><description>Maybe more of the business rules aswell, how do you determine if Joe Doe is really Joe Doe in the other database, both maybe married to a Sue.&lt;img src=icon_smile.gif border=0 align=middle&gt;</description><pubDate>Tue, 22 Jul 2003 15:14:00 GMT</pubDate><dc:creator>5409045121009-7368</dc:creator></item><item><title>RE: Match firstname lastname</title><link>http://www.sqlservercentral.com/Forums/Topic14416-8-1.aspx</link><description>I agree that seeing the schema will up. The logic will might be a bit complex, may have to have more than 1 temp table, but again without the schema (from both databases), it's a hard call. </description><pubDate>Tue, 22 Jul 2003 12:18:00 GMT</pubDate><dc:creator>rnelson_shs</dc:creator></item><item><title>RE: Match firstname lastname</title><link>http://www.sqlservercentral.com/Forums/Topic14416-8-1.aspx</link><description>Instead of trying to compare single column values to multivalue columns, look at using the like operator to search through the multi-value columns looking for instances of the name you are searching. If you post your schema, we can show you the T-SQL. </description><pubDate>Tue, 22 Jul 2003 10:40:00 GMT</pubDate><dc:creator>j.o.s.</dc:creator></item><item><title>Match firstname lastname</title><link>http://www.sqlservercentral.com/Forums/Topic14416-8-1.aspx</link><description>Hi,Could anyone help me with T-SQL to match names. I have to match names from one database to bank account details entered by clients in another. The problem is that clients enter full name, initials, fistname last and lastname first, spouses names etc. for account details. Huge dilemma!Thanks in advance,diesel&lt;img src=icon_smile_blackeye.gif border=0 align=middle&gt;</description><pubDate>Tue, 22 Jul 2003 05:51:00 GMT</pubDate><dc:creator>diesel</dc:creator></item></channel></rss>