"glovemtb" <glovemtb@comcast.net> wrote in message
news:1170252734.250242.135670@a75g2000cwd.googlegroups.com:

> Tools : Sql Server Enterprise 2005 , Visual Studio 2005, SSIS/DTSX,
> oledb datasouces SQL Server 2000.
> Testing the new tools specifically Dtsx Fuzzy lookup tool here is I
> think the bug.
> Entering new values into the reference lookup table and even with the
> "create new index" option selected in Fuzzy Lookup; the new records
> are not correctly matched. Only the original ones in the lookup table.
> Here is step by step to reproduce the issue:
> 1-I simply "select into" to create a "UserLookup" reference table say
> 4 records from a Users table that I want to do fuzzy lookup on the
> Oledb datasouce (Sql Server 2k database) LastName and FirstName are
> the fuzzy lookup criteria columns.
> So the oledb datasource table is Users and the reference table for the
> fuzzy lookup is UserLookup.
> 2- Everything works fine and with a conditional split I get the 4
> matched records in the UserMatch destination and the rest unmatched in
> the UserNomatch tables.
> 3- But, If I edit the UserLookup table, by putting in a new record
> that should match the fuzzy lookup, it does not pick it up when I re-
> run the package. Even with the create new index option on in the fuzzy
> lookup reference table options.
> My question is could this be a index caching issue ?
> Not a good thing if you have lookups on dynamic tables that an
> application is attached to and you expect to be able to edit and place
> in new records all the time to do fuzzy lookups on.
> You would not want to have to dbcc reindex before every fuzzy lookup !
>
> Thanks all