FIX: High memory usage when you run Replication Snapshot Agent in SQL Server 2008 or in SQL Server 2008 R2

Microsoft distributes Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 or SQL Server 2008 R2 update release.

Symptoms

When you run Replication Snapshot Agent in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2, memory usage increases to a high level and Replication Snapshot Agent fails. Additionally, the following error message is logged in the SQL Server Agent error log:

Cause

This issue because Replication Snapshot Agent does not write data to the disk.

When Replication Snapshot Agent uses memory mapped files to process the data, Replication Snapshot Agent usually writes data to the disk. However, the speed of data access is faster than the writing speed. Therefore, Replication Snapshot Agent does not write data to the disk, and the memory usage level increases to a high level.

Resolution

Cumulative update information

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2629969 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 10. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

Cumulative update package 6 for SQL Server 2008 Service Pack 2 (SP2)

The fix for this issue was first released in cumulative update package 6 for SQL Server 2008 SP2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

Note Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 update release. Microsoft recommends that you consider applying the most recent update release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released

Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a hotfix for SQL Server 2008 SP2 on a computer that has SQL Server 2008 SP2 installed.

Note All hotfixes that are in a SQL Server service pack are also included in a later SQL Server service pack.

Cumulative update package 16 for SQL Server 2008 Service Pack 1 (SP1)

The fix for this issue was first released in cumulative update package 16 for SQL Server 2008 SP1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

Note Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 update release. Microsoft recommends that you consider applying the most recent update release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released

Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a hotfix for SQL Server 2008 SP1 on a computer that has SQL Server 2008 SP1 installed.

Note All hotfixes that are in a SQL Server service pack are also included in a later SQL Server service pack.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.