MSSQLSERVER_17890MSSQLSERVER_17890

適用範圍:Applies to: 是SQL ServerSQL Server (所有支援的版本) yesSQL ServerSQL Server (all supported versions) 適用範圍:Applies to: 是SQL ServerSQL Server (所有支援的版本) yesSQL ServerSQL Server (all supported versions)

詳細資料Details

屬性Attribute Value
產品名稱Product Name SQL ServerSQL Server
事件識別碼Event ID 1789017890
事件來源Event Source MSSQLSERVERMSSQLSERVER
元件Component SQLEngineSQLEngine
符號名稱Symbolic Name SRV_WS_TRIMMEDSRV_WS_TRIMMED
訊息文字Message Text SQL Server 處理序記憶體的重要部分已被移出分頁。這可能導致效能變差。A significant part of SQL Server process memory has been paged out. This may result in a performance degradation. 持續時間: %d 秒,Duration: %d seconds. 工作集 (KB): %I64d,已認可 (KB): %I64d,記憶體使用情形: %d%%。Working set (KB): %I64d, committed (KB): %I64d, memory utilization: %d%%.

說明Explanation

您可能會在 SQL ServerSQL Server 錯誤記錄檔或 Windows 應用程式事件記錄檔中遇到下列錯誤訊息。You might encounter the following error message in the SQL ServerSQL Server error log or the Windows Application event log.

SQL Server 處理序記憶體的重要部分已被移出分頁。這可能導致效能變差。A significant part of SQL Server process memory has been paged out. This may result in a performance degradation. 持續時間︰0 秒。Duration: 0 seconds. 工作集 (KB):3383250,已認可 (KB):9112480,記憶體使用情形:37%。Working set (KB): 3383250, committed (KB): 9112480, memory utilization: 37%.

您可能也會注意到,SQL Server 上查詢執行和所有其他作業的效能突然降低。You might also notice a sudden performance degradation with query execution and all other operations on the SQL Server.

原因Cause

SQL ServerSQL Server 會監視有關 SQL ServerSQL Server 處理序的各種記憶體相關資訊。monitors the various memories related information about the SQL ServerSQL Server process. 在此情況下,其已偵測到處理序的工作集小於已認可處理序記憶體的 50%。In this case, it has detected that the working set of the process is less than 50% of the committed process memory. 因此,會列印此警告。As a result this warning is printed. 此警告的一般原因包括:The normal causes of this warning are:

  • 作業系統會將大部分 SQL ServerSQL Server 認可的記憶體移出分頁到分頁檔。The operating system pages out large portions of the SQL ServerSQL Server committed memory to the paging file.
  • 這可能是因為其他應用程式或作業系統需求對於記憶體的需求突然增加所致。This could be due to sudden increased demand for memory from other applications or operating system needs.
  • 當某些裝置驅動程式要求連續記憶體配置以滿足其需求時,可能也會發生此情況。This could also happen when certain device drivers request contiguous memory allocations for their needs.

使用者動作User action

您可以透過鎖定實體記憶體中針對緩衝集區所配置的記憶體,來防止 Windows 作業系統將 SQL ServerSQL Server 處理序的緩衝集區記憶體移出分頁。You can prevent the Windows operating system from paging out the buffer pool memory of the SQL ServerSQL Server process by locking the memory that is allocated for the buffer pool in physical memory. 您可以將 [鎖定記憶體中的分頁] 使用者權限指派給用來作為 SQL ServerSQL Server 服務啟動帳戶的使用者帳戶,以鎖定記憶體。You lock the memory by assigning the Lock pages in memory user right to the user account that is used as the startup account of the SQL ServerSQL Server service. 但在您實作此解決方案之前,請先檢閱導致將 SQL Server 記憶體移出分頁的原因和<重要考量>等小節,然後將 [鎖定記憶體中的分頁] 使用者權限指派給 SQL Server 的執行個體But before you implement this solution, review the sections What causes SQL Server memory to be paged out and Important considerations before you assign the "Lock pages in memory" user right for an instance of SQL Server

注意

使用 [鎖定記憶體中的分頁] 可確保 SQL ServerSQL Server 所管理的記憶體不會被移出分頁。不過,執行緒堆疊、EXE 與任何 DLL 映像、堆積記憶體、CLR 記憶體仍可由 OS 移出分頁。Using Lock Pages in Memory ensure that the memory managed by SQL ServerSQL Server is not paged out. However, thread stacks, the EXE and any DLL images, heap memory, CLR memory can still be paged out by the OS.

SQL ServerSQL Server 2008 SP1 累積更新 2 開始,SQL ServerSQL Server Standard 與 Enterprise 版本都可以使用 [鎖定記憶體中的分頁] 使用者權限。Starting with SQL ServerSQL Server 2008 SP1 Cumulative Update 2, both SQL ServerSQL Server Standard and Enterprise editions can use the Lock pages in memory user right. 如需鎖定分頁支援的詳細資訊,請參閱 KB970070 - SQL Server Standard Edition (64 位元) 系統上對鎖定分頁的支援 (英文)。For more information about support for locked pages, view KB970070 - Support for Locked Pages on SQL Server Standard Edition (64-bit) systems.

若要指派 [鎖定記憶體中的分頁] 使用者權限,請遵循下列步驟:To assign the Lock pages in memory user right, follow these steps:

  1. 依序按一下 [開始] 與 [執行]、輸入 gpedit.msc,然後按一下 [確定]。Click Start, click Run, type gpedit.msc, and then click OK.
  2. 請注意,[群組原則] 對話方塊隨即出現。Note The Group Policy dialog box appears.
  3. 依序展開 [電腦設定] 與 [Windows 設定]。Expand Computer Configuration, and then expand Windows Settings.
  4. 展開 [安全性設定],然後展開 [本機原則]。Expand Security Settings, and then expand Local Policies.
  5. 按一下 [使用者權限指派],然後按兩下 [鎖定記憶體中的分頁]。Click User Rights Assignment, and then double-click Lock pages in memory.
  6. 在 [本機安全性原則設定] 對話方塊中,按一下 [新增使用者或群組] 。In the Local Security Policy Setting dialog box, click Add User or Group.
  7. 在 [選取使用者或群組] 對話方塊中,新增具有執行 Sqlservr.exe 檔案權限的帳戶,然後按一下 [確定]。In the Select Users or Groups dialog box, add the account that has permission to run the Sqlservr.exe file, and then click OK.
  8. 關閉 [群組原則] 對話方塊。Close the Group Policy dialog box.
  9. 重新啟動 SQL ServerSQL Server 服務。Restart the SQL ServerSQL Server service.

當您指派 [鎖定記憶體中的分頁] 使用者權限並重新啟動 SQL ServerSQL Server 服務之後,Windows 作業系統就不會再在 SQL ServerSQL Server 處理序中將緩衝集區記憶體移出分頁。After you assign the Lock pages in memory user right and you restart the SQL ServerSQL Server service, the Windows operating system no longer pages out the buffer pool memory within the SQL ServerSQL Server process. 不過,Windows 作業系統仍然可以在 SQL ServerSQL Server 處理序中將非緩衝集區記憶體移出分頁。However, the Windows operating system can still page out the nonbuffer pool memory within the SQL ServerSQL Server process.

您可以在啟動時,透過確認已將下列訊息寫入 SQL ServerSQL Server 錯誤記錄檔,來驗證 SQL ServerSQL Server 執行個體所使用的使用者權限:「針對緩衝集區使用鎖定分頁」You can validate that the user right is used by the instance of SQL ServerSQL Server by making sure that the following message is written in the SQL ServerSQL Server Error Log at startup: "Using locked pages for buffer pool"

此訊息只適用 SQL Server。This message applies only to SQL Server. 如需有關錯誤記錄檔中此訊息的詳細資訊,請參閱下列文章:我是否必須在本機系統中指派 [鎖定記憶體中的分頁] 權限 (英文)For more information about this message in the ERRORLOG, visit the following: Do I have to assign the Lock pages for Memory privilege in Local System

當 Windows 作業系統將非緩衝集區記憶體移出分頁時,您可能還是會遇到效能問題。When the Windows operating system pages out the nonbuffer pool memory, you may still encounter performance issues. 不過,<說明>一節中所述的錯誤訊息不會記錄於 SQL ServerSQL Server 錯誤記錄檔中。However, the error messages that are mentioned in the "Explanation" section are not logged in the SQL ServerSQL Server error log.

導致將 SQL Server 記憶體移出分頁的原因What causes SQL Server memory to be paged out

可能導致此問題的問題可分為三大類:There are three broad categories of problems that can cause this issue:

  • 應用程式相關問題:所有應用程式一起耗盡了可用實體記憶體,而 OS 必須釋放一些記憶體,以供新應用程式對資源的要求使用。Application-Related Issues: All applications together have exhausted the available physical memory and the OS must free some memory for new application requests for resources. 一般來說,這裡所述的方法是,尋找哪些應用程式會耗盡記憶體,並採取必要步驟來平衡記憶體,使其不會導致 RAM 耗盡。Typically, the approach here is to find what applications are exhausting the memory and take necessary steps to balance the memory among them without leading to RAM exhaustion.
  • 裝置驅動程式問題:如果驅動程式呼叫記憶體配置函式的方式不正確,裝置驅動程式可能會導致對所有處理序的工作集進行分頁。Device Driver Issues: Device Drivers may cause working set paging of all processes if the driver calls a memory allocation function incorrectly.
  • 作業系統問題Operation System Issues

您可以在下面找到這其中每個類別的相關資訊Below, you can find information on each of these categories

  • 應用程式相關問題:這些應用程式一起可能會耗用系統上的所有 RAM。Application-Related issues: Applications together may consume all of the RAM on the system. 如果對記憶體提出新要求,OS 就會嘗試滿足新要求,但如果沒有可用記憶體,其將會修剪執行中應用程式的工作集來滿足記憶體要求。If new requests for memory are made, the OS attempts to satisfy them and if there is no free memory, it will trim the working set of running applications to satisfy the memory requests. 在這種情況下,您可能會觀察到,即使不是所有應用程式,大部分應用程式的工作集都會顯著下降。In such cases, you may observe that the working set for most if not all applications drop significantly. 若要觀察此情況,請針對系統上的所有應用程式收集下列效能監視器計數器:To observe this, collect the following Performance Monitor counter for all applications on the system:

    • 效能物件:ProcessPerformance object: Process
    • 計數器:工作集Counter: Working Set

    此外,請監視下列計數器,以相互關聯系統上可用的實體記憶體數量。Also, monitor the following counter to correlate how much physical memory is available on the system.

    • 效能物件:記憶體Performance object: Memory
    • 計數器:可用的記憶體 (MB)Counter: Available Memory (MB)

    您可能會觀察到的典型行為是可用的記憶體降低到接近 0 MB,同時系統上大部分 (全部) 處理序的工作集計數器也會突然下降。The typical behavior that you may observe is reduction of Available memory close to 0 MB while at the same time a sudden drop of the Working Set counters for most (all) processes on the system. 如果您觀察到此類行為,則可能需要採取步驟來降低系統上的記憶體使用率,包括減少 SQL Server 的「最大伺服器記憶體」。If you observe such behavior, you may need to take steps to reduce memory usage on the system, which includes for example reducing Max Server Memory for SQL Server.

    應用程式可能也會使用太多系統快取,而且可能造成系統快取的大幅增長。Applications may also use the system cache too much, and may cause a large growth of the system cache. 為了回應系統快取的增長,系統會將 SQL ServerSQL Server 處理序或其他應用程式的工作集移出分頁。To respond to the growth of the system cache, the system pages out the working set of the SQL ServerSQL Server process or of other applications. 如果您遇到此問題,則可在應用程式中使用一些記憶體管理函式。If you experience this problem, you can use some memory management functions in the application. 這些函式會控制檔案 I/O 作業可在應用程式中使用的系統快取空間。These functions control the system cache space that file I/O operations can use in the application. 例如,您可以使用 SetSystemFileCacheSize 函式與 GetSystemFileCacheSize 函式,來控制檔案 I/O 作業可以使用的系統快取空間。For example, you can use the SetSystemFileCacheSize function and the GetSystemFileCacheSize function to control the system cache space that file I/O operations can use.

    您可以使用記憶體效能物件來檢視此物件中各種計數器的值,以判斷系統快取工作集是否使用太多記憶體。You can use the Memory performance object to view the values of various counters in this object to determine whether the system cache working set uses too much memory. 例如,您可以檢視 Cache Bytes 與 System Cache Resident Bytes 計數器。For example, you can view the Cache Bytes and System Cache Resident Bytes counters. 如需此主題的詳細資訊,請參閱:For more information about this topic, see:

    您可以下載並部署「Microsoft Windows 動態快取服務」,以控制系統快取所耗用的記憶體。You can download and deploy the "Microsoft Windows Dynamic Cache Service" to control the memory that is consumed by the system cache.

  • 裝置驅動程式問題:如果裝置驅動程式使用 MmAllocateContiguousMemory 函式,而且如果將 HighestAcceptableAddress 參數的值設定為小於 4 GB,則 Windows 作業系統可能會將系統上處理序 (包括 SQL ServerSQL Server 處理序) 的工作集移出分頁。Device Driver Issues: If a device driver uses the MmAllocateContiguousMemory function, and if it sets the value of the HighestAcceptableAddress parameter to less than 4 gigabytes (GB), the Windows operating system may page out the working set of the processes on the system including SQL ServerSQL Server process. 若要解決此問題,請連絡裝置驅動程式的廠商以取得驅動程式更新。To resolve this problem, contact the vendor of the device driver for driver updates.

    當裝置驅動程式嘗試配置記憶體時,Windows 作業系統可能會將其他應用程式的工作集移出分頁。When a device driver tries to allocate memory, the Windows operating system may page out the working set of other applications. 此 Windows Hotfix 可讓您使用事件追蹤來尋找導致問題的裝置驅動程式。This Windows hotfix lets you use event tracing to find the device driver that causes problem. 若要尋找導致工作集修剪行為之特定驅動程式的詳細資訊,請參閱識別配置連續記憶體的驅動程式To find more information about the specific driver that causes the working set trimming behavior, see Identifying Drivers That Allocate Contiguous Memory.

  • 作業系統問題:若要解決造成 Windows 作業系統將 SQL ServerSQL Server 處理序的工作集移出分頁的已知問題,請套用下列 Microsoft 知識庫文件中所述的 Hotfix。Operating System Issues: To resolve the known issues that cause the Windows operating system to page out the working set of the SQL ServerSQL Server process, apply the hotfixes that are described in the following Microsoft Knowledge Base articles.

    注意

    Hotfix 是累積的。Hotfixes are cumulative. 較新版本的 Hotfix 包含該 Hotfix 的較舊版本。A later version of a hotfix contains the earlier versions of that hotfix.

指派 [鎖定記憶體中的分頁] 使用者權限之前的重要考量Important considerations before you assign the "Lock pages in memory" user right

指派 [鎖定記憶體中的分頁] 使用者權限之前,您應該先進行其他考量。You should make additional considerations before you assign the Lock pages in memory user right. 如果您在設定錯誤的系統上指派此使用者權限,系統可能會變得不穩定,或遇到整個系統的效能降低。If you assign this user right on systems that are configured incorrectly, the system may become unstable or experience a performance decrease of the whole system. 此外,事件記錄檔中可能會記錄事件識別碼 333。Additionally, event ID 333 may be logged in the event log.

如果您與 Microsoft 客戶支援服務 (CSS) 連絡以解決這些問題,CSS 工程師可能會要求您針對用來作為 SQL ServerSQL Server 服務啟動帳戶的使用者帳戶撤銷此使用者權限。If you contact Microsoft Customer Support Service (CSS) for these problems, CSS engineers may ask you to revoke this user right for the user account that is used as the startup account of the SQL ServerSQL Server service. 這對收集重要效能資料而言可能是必要步驟,讓 CSS 工程師可用來針對 SQL ServerSQL Server 的各種選項,以及其他在系統上執行的應用程式進行必要設定。This step may be necessary to collect important performance data that CSS engineers can use for necessary configuration of the various options for SQL ServerSQL Server and for other applications that are running on the system. 在 CSS 工程師收集效能資料之後,您就可以將 [鎖定記憶體中的分頁] 使用者權限指派給 SQL ServerSQL Server 服務的啟動帳戶。After CSS engineers collect the performance data, you can assign the Lock pages in memory user right to the startup account of the SQL ServerSQL Server service.

指派 [鎖定記憶體中的分頁] 使用者權限之前,請務必擷取效能監視器記錄,以判斷系統上安裝的各種應用程式與服務的記憶體需求。Before you assign the Lock pages in memory user right, make sure that you capture a Performance Monitor log to determine the memory requirements of various applications and services that are installed on the system. 這些應用程式也包括 SQL Server。These applications also include SQL Server. 為了判斷記憶體需求,請收集下列基準資訊:To determine the memory requirements, collect the following baseline information:

  • 確定您已正確設定 [最大伺服器記憶體] 選項與 [最小伺服器記憶體] 選項。Make sure that you set the max server memory option and the min server memory option correctly. 這些選項只會反映 SQL ServerSQL Server 處理序之緩衝集區的記憶體需求。These options reflect only the memory requirement of the buffer pool of the SQL ServerSQL Server process. 這些選項未包含為 SQL ServerSQL Server 處理序內的其他元件所配置的記憶體。These options do not include the memory that is allocated for other components within the SQL ServerSQL Server process. 這些元件包括下列項目:These components include the following:

    • SQL ServerSQL Server 背景工作執行緒The SQL ServerSQL Server worker threads
    • SQL ServerSQL Server 處理序會在 SQL ServerSQL Server 處理序的位址空間中載入的各種 DLL 與元件Various DLLs and components that the SQL ServerSQL Server process loads within the address space of the SQL ServerSQL Server process
    • 備份與還原作業The Backup and restore operations
  • DLL 與元件包括各種 OLE DB 提供者、擴充預存程序、用於 sp_OACreate 預存程序的 Microsoft COM 物件、連結的伺服器與 SQL ServerSQL Server CLR。The DLLs and components include various OLE DB providers, extended stored procedures, Microsoft COM objects that are used for the sp_OACreate stored procedure, linked servers, and SQL ServerSQL Server CLR. 為這些元件配置的記憶體會落在 SQL ServerSQL Server 處理序位址空間的非緩衝集區區域底下。Memory that is allocated for these components falls under the nonbuffer pool region of the address space of the SQL ServerSQL Server process. 若要理想地判斷整個 SQL ServerSQL Server 處理序可使用的記憶體數量上限,您必須從希望 SQL ServerSQL Server 處理序使用的記憶體總數中減去配置給未使用緩衝集區之元件的記憶體。To ideally determine the maximum amount of memory that the whole SQL ServerSQL Server process can use, you must subtract the memory that is allocated for components that do not use the buffer pool from the total memory that you want the SQL ServerSQL Server process to use. 然後,您可以使用餘數值來設定 [最大伺服器記憶體] 選項。Then, you can use the remainder value to set the max server memory option. 設定 [最大伺服器記憶體] 選項與 [最小伺服器記憶體] 選項之前,請仔細參閱《SQL ServerSQL Server 線上叢書》中的<手動設定記憶體選項>主題。Before you set the max server memory option and the min server memory option, you should carefully review the "Setting the memory options manually" topic in SQL ServerSQL Server Books Online.

  • 判斷其他應用程式與 Windows 作業系統元件的記憶體需求。Determine the memory requirement of other applications and of the Windows operating system components. 應用程式可能包含其他 SQL ServerSQL Server 元件,例如 SQL ServerSQL Server Agent、SQL ServerSQL Server 複寫代理程式、SQL ServerSQL Server Reporting Services、SQL ServerSQL Server Analysis Services、SQL ServerSQL Server Integration Services 與 SQL ServerSQL Server 全文檢索搜尋。Applications may include other SQL ServerSQL Server components, for example, SQL ServerSQL Server Agent, SQL ServerSQL Server Replication Agents, SQL ServerSQL Server Reporting Services, SQL ServerSQL Server Analysis Services, SQL ServerSQL Server Integration Services, and SQL ServerSQL Server Full Text Search. 執行備份作業與檔案複製作業的應用程式可能會使用大量記憶體。Applications that perform Backup operations and file copy operations may use lots of memories. 請將大量複製及產生檔案 IO 之快照集代理程式等作業納入考量。Consider operations such as bulk copy and the Snapshot Agent that generate file IO. 當您判斷 [最大伺服器記憶體] 選項與 [最小伺服器記憶體] 選項的值時,必須考慮所有這些應用程式的記憶體需求。You must consider the memory requirement of all these applications when you determine the value of the max server memory option and of the min server memory option. 您可以在每個處理序的 [處理序] 物件底下,使用 Private Bytes 計數器與 Working Set 計數器來判斷特定處理序的記憶體需求。You can use the Private Bytes counter and the Working Set counter under the Process object for every process to determine the memory requirement for a specific process.

  • 預設已將 [鎖定記憶體中的分頁] 使用者權限指派給內建的本機系統帳戶。By default, the Lock pages in memory user right have already been assigned to the built-in Local System account. 如需詳細資訊,請瀏覽下列 Microsoft 網站:我是否必須針對本機系統指派 [鎖定記憶體中的分頁] 權限 (英文)For more information, visit the following Microsoft Web site: Do I have to assign the Lock pages in Memory privilege for Local system?

  • 如果您針對網域中的所有 SQL ServerSQL Server 處理序全域使用 Windows 使用者帳戶,請使用群組原則設定來判斷要指派的使用者權限。If you use a Windows user account globally for all SQL ServerSQL Server processes in a domain, determine the user rights that are assigned by using a Group Policy configuration. 32 位元的 SQL ServerSQL Server 處理序可能會使用此帳戶作為啟動帳戶。A 32-bit SQL ServerSQL Server process may use this account as the startup account. 不過,此帳戶需要 [鎖定記憶體中的分頁] 使用者權限,才能啟用 Address Windowing Extensions (AWE) 功能。However, this account requires the Lock pages in memory user right to enable the Address Windowing Extensions (AWE) feature. 如需詳細資訊,請參閱《SQL ServerSQL Server 線上叢書》中的<為 SQL Server 提供最大的記憶體數量>主題。For more information, see the "Providing the maximum amount of memory to SQL Server" topic in SQL ServerSQL Server Books Online.

  • 在您為多個 SQL ServerSQL Server 執行個體設定 [最大伺服器記憶體] 選項與 [最小伺服器記憶體] 選項之前,請考慮針對每個 SQL Server 執行個體的非緩衝集區記憶體需求。Before you configure the max server memory option and the min server memory option for multiple SQL ServerSQL Server instances, consider the memory requirements of the nonbuffer pool for each instance of SQL Server. 然後,針對每個 SQL Server 執行個體設定這些選項。Then, configure these options for each instance of SQL Server.

在理想的情況下,您會在尖峰負載期間收集此基準資訊。Ideally, you collect this baseline information during peak loads. 因此,您可以判斷各種應用程式與元件的記憶體需求,以支援尖峰負載。Therefore, you can determine the memory requirements for various applications and components to support the peak load. 視系統上執行的活動和應用程式而定,記憶體需求會因系統而異。The memory requirements vary from one system to another system, depending on the activities and the applications that are running on the system. 您可以查詢動態管理檢視 sys.dm_os_process_memory 中提供的資訊,以了解系統是否遇到記憶體不足的狀況。You can query the information that is provided in the dynamic management view sys.dm_os_process_memory to understand whether the system is encountering low memory conditions. 如需詳細資訊,請參閱 sys.dm_os_process_memory (Transact-SQL)For more information, see sys.dm_os_process_memory (Transact-SQL).

Windows Server 2008 與 R2 版本中新增的改進Improvements added in Windows Server 2008 and R2 version

Windows Server 2008 與 Windows Server 2008 R2 改進了連續記憶體配置機制。Windows Server 2008 and Windows Server 2008 R2 improve the contiguous memory allocation mechanism. 此改進讓 Windows Server 2008 與 Windows Server 2008 R2 能夠在新的記憶體要求抵達時,在一定程度上降低將應用程式的工作集移出分頁的影響。This improvement lets Windows Server 2008 and Windows Server 2008 R2 reduce to a certain extent the effects of paging out the working set of applications when new memory requests arrive.

以下說明 Microsoft 白皮書<Windows 中記憶體管理的進展>中的改進:The following is an explanation of the improvements from the Microsoft whitepaper "Advances in Memory Management in Windows":

在 Windows Server 2008 中,已大幅增強實體連續記憶體的配置。配置連續記憶體的要求較可能成功,因為記憶體管理員現在可以動態取代分頁,通常不需修剪工作集或執行 I/O 作業。此外,許多其他類型的分頁 (例如,核心堆疊與檔案系統中繼資料分頁等) 現在都是要用來取代的候選項目。因此,在任何指定的時間,通常會有更多連續記憶體可供使用。此外,取得這類配置的成本會大幅降低。In Windows Server 2008, the allocation of physically contiguous memory is greatly enhanced. Requests to allocate contiguous memory are much more likely to succeed because the memory manager now dynamically replaces pages, typically without trimming the working set or performing I/O operations. In addition, many more types of pages—such as kernel stacks and file system metadata pages, among others—are now candidates for replacement. Consequently, more contiguous memory is generally available at any given time. In addition, the cost to obtain such allocations is greatly reduced.

如需詳細資訊,請參閱 SQL Server 工作集修剪問題 (英文)。For more information, view SQL Server Working Set Trim Problems.

本文章討論的協力廠商產品是由獨立於 Microsoft 的公司製造。The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft 對於這些產品的效能或可靠性不提供任何默示或其他保證。Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.