FIX: A database page is copied into a database snapshot even though the page is not updated when you perform a read operation in SQL Server 2008 or in SQL Server 2008 R2

Article ID: 2625768 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 or 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 fixes that were included with the previous SQL Server 2008 or SQL Server 2008 R2 fix release.
Expand all | Collapse all

On This Page

Symptoms

Assume that you perform a read operation on a Microsoft SQL Server 2008 or SQL Server 2008 R2 database page. The database page is not updated after a database snapshot is created.

In this situation, the database page is copied into the database snapshot.

Note This issue causes errors when the database is large and when many read and write operations occur. For example, if you run DBCC CHECKDB against the database when the size of the sparse file in the database snapshot exceeds the size limitation of the NTFS file system, you might receive the following error message:
Operating system error 665
Back to the top | Give Feedback

Cause

This issue occurs because a transient change happens in the page header when you perform a read operation on the database page. Therefore, the database page is considered as updated and is copied into the snapshot.
Back to the top | Give Feedback

Resolution

Cumulative update information

SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. 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:
2720425
(http://support.microsoft.com/kb/2720425/ )
Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 2
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:
2730301
(http://support.microsoft.com/kb/2730301/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 6 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:
2715953
(http://support.microsoft.com/kb/2715953/LN/ )
Cumulative update package 6 for SQL Server 2008 Service Pack 3
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
(http://support.microsoft.com/kb/2629969/LN/ )
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 Service Pack 1

The fix for this issue was first released in Cumulative Update 7 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:
2703282
(http://support.microsoft.com/kb/2703282/ )
Cumulative Update package 7 for SQL Server 2008 R2 Service Pack 1
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
(http://support.microsoft.com/kb/2567616/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 14. 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:
2703280
(http://support.microsoft.com/kb/2703280/ )
Cumulative Update package 14 for SQL Server 2008 R2
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
(http://support.microsoft.com/kb/981356/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

To resolve this issue, follow these steps:
  1. Download and install the hotfix that is described in the following article in the Microsoft Knowledge Base:

    967351
    (http://support.microsoft.com/kb/967351/en-us/ )
    A heavily fragmented file in an NTFS volume may not grow beyond a certain size
  2. Format the drive that will host the snapshot. To do this, type the following command at a command prompt, and then press Enter:

    Format drive_lettter /FS:NTFS /L
Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

References

For more information about how database snapshots work, visit the following MSDN website:
Information about how database snapshots work
(http://msdn.microsoft.com/en-us/library/ms187054(v=sql.100).aspx)
For more information about sparse files in database snapshots, visit the following MSDN website:
Information about sparse files in database snapshots
(http://msdn.microsoft.com/en-us/library/ms175823(v=sql.100).aspx)
Back to the top | Give Feedback

Properties

Article ID: 2625768 - Last Review: August 1, 2012 - Revision: 5.0
Applies to
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Web
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Web
  • Microsoft SQL Server 2008 R2 Workgroup
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2625768
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top