Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Memory leak when DPA monitors a SQL Server 2017 database instance with large page support enabled

Memory leak when DPA monitors a SQL Server 2017 database instance with large page support enabled

Updated April 3, 2018

Overview

When DPA monitors a SQL Server 2017 database instance, it's possible for a memory leak to develop on the server if trace flag 834 is turned on. Trace flag 834 enables large page support. 

Environment

  • DPA, all versions
  • The monitored database instance is SQL Server 2017
  • The database instance runs on a server with trace flag 834 turned on

Cause

Microsoft has confirmed that this is an issue with SQL Server 2017. 

Resolution

To resolve this issue, turn off trace flag 834.

 

 

Last modified

Tags

Classifications

Public