To ensure that foldable Power Query transformation steps are processed by the Microsoft SQL Server engine during ingestion from Azure SQL, which configuration should you apply?

To ensure that foldable Power Query transformation steps are processed by the Microsoft SQL Server engine during ingestion from Azure SQL, which configuration should you apply?

• A. NativeQuery and EnableFolding
• B. NativeQuery and StopFolding
• C. Table and EnableFolding
• D. Table and StopFolding

Answer: (A)

Power Query folding pushes transformations to the data source so the server runs them. When ingesting from Azure SQL, you want the query to be executed on SQL Server and allow as many steps as possible to fold back into that server-side query. Using a native query tells Power Query to send a SQL query to the server, and enabling folding allows the subsequent transformation steps to be folded into that server-side query. Together, NativeQuery with EnableFolding ensures the foldable steps are processed by the SQL Server engine during ingestion. Choosing StopFolding or using a Table source would cause work to be done on the Power Query side rather than pushed to SQL Server, breaking the goal of server-side processing.

Power Query folding pushes transformations to the data source so the server runs them. When ingesting from Azure SQL, you want the query to be executed on SQL Server and allow as many steps as possible to fold back into that server-side query. Using a native query tells Power Query to send a SQL query to the server, and enabling folding allows the subsequent transformation steps to be folded into that server-side query. Together, NativeQuery with EnableFolding ensures the foldable steps are processed by the SQL Server engine during ingestion.

Choosing StopFolding or using a Table source would cause work to be done on the Power Query side rather than pushed to SQL Server, breaking the goal of server-side processing.