Last updated on May 1, 2026
You may know, this issue has already been resolved by new SQL SERVER 2025 Standard Developer Edition.
However in case of 2019 version you can use those hints in query for the simulation:
option (use hint ('disable_batch_mode_adaptive_joins'),
use hint ('disable_batch_mode_memory_grant_feedback'),
use hint ('disable_interleaved_execution_tvf'),
use hint ('disable_deferred_compilation_tv'),
use hint ('disable_tsql_scalar_udf_inlining'))
or database scope settings:
ALTER DATABASE SCOPED CONFIGURATION SET BATCH_MODE_ON_ROWSTORE = OFF;
ALTER DATABASE SCOPED CONFIGURATION SET ROW_MODE_MEMORY_GRANT_FEEDBACK = OFF;
ALTER DATABASE SCOPED CONFIGURATION SET BATCH_MODE_MEMORY_GRANT_FEEDBACK = OFF;
ALTER DATABASE SCOPED CONFIGURATION SET CE_FEEDBACK = OFF;
ALTER DATABASE SCOPED CONFIGURATION SET DOP_FEEDBACK = OFF;
ALTER DATABASE SCOPED CONFIGURATION SET AUTOMATIC_TUNING = OFF;
ALTER DATABASE SCOPED CONFIGURATION SET AUTOMATIC_TUNING (FORCE_LAST_GOOD_PLAN = OFF);
ALTER DATABASE SCOPED CONFIGURATION SET ACCELERATED_PLAN_FORCING = OFF;
All this was consulted a partially code was provided by Microsoft Copilot, don’t hesitate to ask for further details.
Intelligent Query Processing – SQL Server | Microsoft Learn
