Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. A "Failed to reserve contiguous memory" error message may be logged in the SQL Server error log when users connect to an instance of SQL Server by using a network packet size that is larger than 8,060 bytes

A "Failed to reserve contiguous memory" error message may be logged in the SQL Server error log when users connect to an instance of SQL Server by using a network packet size that is larger than 8,060 bytes

Symptoms

In Microsoft SQL Server 2000 and in SQL Server 2005, when users connect to an instance of SQL Server by using a network packet size that is larger than 8,060 bytes, an error message that is similar to the following may be logged in the SQL Server error log:
WARNING: Failed to reserve contiguous memory of Size= <allocation_size>. ... Dynamic Memory Manager: Stolen=xx OS Reserved=<reserved pages> OS Committed=<committed pages> OS In Use=<in use pages>
This problem occurs when
<allocation_size> is larger than or equal to 65,536 and <reserved pages>,
<committed pages>, and <in use pages> are larger than 100 MB.

↑ Back to the top

Cause

This problem occurs because network packet sizes that are larger than 8,060 bytes require SQL Server to allocate memory from a region of memory that uses a size of 384 MB.

Note By default, the Microsoft .NET Framework Data Provider for SQL Server sets the network packet size to 8,192 bytes.

↑ Back to the top

Resolution

To resolve this problem, specify a network packet size that is smaller than 8,060 bytes. For example, for a .NET Framework Data Provider for SQL Server connection, add the following property to your connection string:
Packet Size=4096

↑ Back to the top

More Information

The network packet size of a client connection can be determined by monitoring the Audit Login event or the
ExistingConnection event in SQL Profiler. The Integer Data data column contains the network packet size.

For more information about how to monitor events by using SQL Profiler, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/aa173918(SQL.80).aspx

↑ Back to the top

Keywords: kbnetwork, kbdatabase, kbtshoot, kbentirenet, kbprb, kb, misc_migrate_32718

↑ Back to the top

Article Info
Article ID : 903002
Revision : 3
Created on : 4/13/2018
Published on : 4/13/2018
Exists online : False
Views : 227