You need to configure the Fuzzy Lookup transformation in the most efficient manner

You are designing a SQL Server Integration Services (SSIS) package that uses the Fuzzy
Lookup transformation.
The reference data to be used in the transformation changes with every package execution.
Common language runtime (CLR) integration cannot be enabled on the SQL Server
database where the reference table is located.
You need to configure the Fuzzy Lookup transformation in the most efficient manner.
What should you do?

You are designing a SQL Server Integration Services (SSIS) package that uses the Fuzzy
Lookup transformation.
The reference data to be used in the transformation changes with every package execution.
Common language runtime (CLR) integration cannot be enabled on the SQL Server
database where the reference table is located.
You need to configure the Fuzzy Lookup transformation in the most efficient manner.
What should you do?

A.
Execute the sp_FuzzyLookupTableMaintenanceInvoke stored procedure.

B.
Select the GenerateNewIndex option in the Fuzzy Lookup Transformation Editor.

C.
Execute the sp_FuzzyLookupTableMaintenanceUninstall stored procedure.

D.
Select the GenerateAndPersistNewIndex option in the Fuzzy Lookup Transformation
Editor.



Leave a Reply 8

Your email address will not be published. Required fields are marked *


Will

Will

“The reference data to be used in the transformation changes with every package execution”.
For me, it indicates that we should not use a Persistant index, so, Answer B for me, no?

Razo

Razo

Will- That’s right.

!aMbo

!aMbo

Will is right.

for changing reference data – GenerateNewIndex option
for fix reference data – GenerateAndPersistNewIndex option

Ale

Ale

I think that the most efficient manner references to d answer, just for not reloading data on every execution

Jianpeng Ji

Jianpeng Ji

Agree with Will
“The reference data to be used in the transformation changes with every package execution.”