Tuesday, April 17, 2012 9:58 AM
Please help me to check on this fuzzy lookup issue.
I have selected to store and maintain index for first time, it works fine (just input 4 variables and look-up from table which contains 1 million records). After execution, I altered the option to use existing index to do the same thing but receive the error msg.
SQL Server 2012 RC0 env. & SSDT development env.
[Fuzzy Lookup ] Warning: Catastrophic failure
[SSIS.Pipeline] Error: Fuzzy Lookup failed the pre-execute phase and returned error code 0x8000FFFF.
I try to reduce my look-up table into 500,000 record, and it works fine by using existing index, but I don't know why??...
Should I change any settings about memory allocation(I set MaxMemoryUsage to 0)? Or may be about RC0 issue?
I have changed WarmCaches property to False but not works.... could anyone give some suggestions?
Thanks in advanced.
Tuesday, April 17, 2012 10:03 AM
I believe RC is not supported anymore as RTM is out. Please try it with RTM version and if the problem is still exists you should post your DDL, and teh SSIS dtsx xml for us to test it.
I hope it helps.
There are 10 type of people. Those who understand binary and those who do not.
Thursday, April 19, 2012 8:37 AM
Thanks for your suggestion, after installed the 2012 RTM version, the package still go wrong with the same error message while using existing index.
And I also found the weird thing when I try to use the drop down list to choose the index which created before, the list always show "Loading...", does anyone could tell me where is the problem here?
Thanks in advanced.
Friday, April 20, 2012 9:53 AMModeratorHi Jack,
When you select Maintain stored index on the Reference Table tab of the Fuzzy Lookup Transformation Editor, the transformation uses managed stored procedures to maintain the index. These managed stored procedures use the common language runtime (CLR) integration feature in SQL Server. By default, CLR integration in SQL Server is not enabled. To use the Maintain stored index functionality, you must enable CLR integration. For more information, see Enabling CLR Integration.
Because the Maintain stored index option requires CLR integration, this feature works only when you select a reference table on an instance of SQL Server where CLR integration is enabled.
For more information about Fuzzy Lookup Transformation, please refer to:
Monday, April 23, 2012 3:50 AM
Thanks for your information, about enable CLR Integration, I have already set it on as below.
Monday, May 14, 2012 10:12 AM
Finally I solved this issue by clicking some options of the Comparison Flags in Fuzzy Lookup component.
Just for your reference, http://msdn.microsoft.com/en-us/library/ms141038
Thanks for all your help.
- Marked As Answer by Jackie_tw Monday, May 14, 2012 10:12 AM
Wednesday, May 16, 2012 12:23 AMModeratorHi Jack,
Thank you for sharing your solutions and experience here. It will be very beneficial for other community members who have similar questions.
Friday, May 17, 2013 3:09 PM
I am experiencing this same issue, can you describe in a little bit more detail what you did with the Comparison Flags to get this to work?
Monday, May 20, 2013 1:57 PMFor anybody else that might see this issue after running the SSIS package once to create the index and then switching it to use the existing index- you have to turn off the WarmCache feature. I beat my head against the wall for 2 days and all you have to do is change that option.