nerdexam
Microsoft

70-463 · Question #240

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…

The correct answer is B. Select the GenerateNewIndex option in the Fuzzy Lookup Transformation Editor. When reference data changes every execution and CLR integration is disabled, the GenerateNewIndex option rebuilds the match index each run without persisting it, avoiding CLR-dependent maintenance.

Extract and transform data

Question

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?

Options

  • AExecute the sp_FuzzyLookupTableMaintenanceInvoke stored procedure.
  • BSelect the GenerateNewIndex option in the Fuzzy Lookup Transformation Editor.
  • CExecute the sp_FuzzyLookupTableMaintenanceUninstall stored procedure.
  • DSelect the GenerateAndPersistNewIndex option in the Fuzzy Lookup Transformation Editor.

How the community answered

(57 responses)
  • A
    19% (11)
  • B
    65% (37)
  • C
    5% (3)
  • D
    11% (6)

Why each option

When reference data changes every execution and CLR integration is disabled, the GenerateNewIndex option rebuilds the match index each run without persisting it, avoiding CLR-dependent maintenance.

AExecute the sp_FuzzyLookupTableMaintenanceInvoke stored procedure.

sp_FuzzyLookupTableMaintenanceInvoke is a CLR-based stored procedure that incrementally updates a persisted index, and it cannot be executed when CLR integration is disabled on the server.

BSelect the GenerateNewIndex option in the Fuzzy Lookup Transformation Editor.Correct

GenerateNewIndex builds a fresh match index at the start of each package execution using the current state of the reference table, ensuring the Fuzzy Lookup always operates against up-to-date data. Because the index is not persisted to disk, the CLR-based index maintenance stored procedures are never invoked, which satisfies the constraint that CLR integration cannot be enabled. This is the most efficient configuration that is both correct and compatible with the given environment restrictions.

CExecute the sp_FuzzyLookupTableMaintenanceUninstall stored procedure.

sp_FuzzyLookupTableMaintenanceUninstall removes existing fuzzy lookup index infrastructure from the database rather than configuring the transformation to handle changing reference data each execution.

DSelect the GenerateAndPersistNewIndex option in the Fuzzy Lookup Transformation Editor.

GenerateAndPersistNewIndex saves the index to the database for reuse across executions, but maintaining this persisted index requires CLR integration, which is explicitly disabled in this scenario.

Concept tested: Fuzzy Lookup index options when CLR integration is disabled

Source: https://learn.microsoft.com/en-us/sql/integration-services/data-flow/transformations/fuzzy-lookup-transformation

Topics

#Fuzzy Lookup#index generation#CLR integration#transformation configuration

Community Discussion

No community discussion yet for this question.

Full 70-463 Practice