Edit

Share via

Interoperability issues between batch mode processing and large page memory model

  • Article

This article helps you resolve the performance and stability issues that arise from the use of batch mode processing on columnstore and rowstore with large page memory model in SQL Server.

Original product version:   SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, SQL Server 2019, SQL Server 2022
Original KB number:   3210239

Symptoms

In this scenario, you experience one or more of the following issues:

  • A non-yielding Scheduler error and associated memory dumps in the SQL Server Error log.

  • Queries that use batch mode processing may run into severe performance issues.

  • Access violation exceptions and associated memory dumps in the SQL Server Error log.

  • You may see the following error message when you run sp_createstats:

    There is insufficient system memory in resource pool 'default' to run this query

Workaround

To mitigate these issues, try either or both of the following two methods:

  • Disable the large page memory model by removing the trace flag 834 (-T834) from SQL Server startup parameters on the SQL Server instance. When you complete this step, SQL Server stops using a large page memory model and reverts to a conventional or lock pages memory model.

  • If you don't use columnstore indexes in your SQL Server and you experience the described symptoms, you can disable batch mode on rowstore at the database level by using ALTER DATABASE SCOPED CONFIGURATION SET BATCH_MODE_ON_ROWSTORE = OFF. For more information, see ALTER DATABASE SCOPED CONFIGURATION.

More information