Microsoft distributes Microsoft SQL Server 2008 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 fix release.
Symptoms
When you run a query against a partitioned table that has data compression enabled in Microsoft SQL Server 2008, database corruption may occur. When this issue occurs, an error message that resembles the following is logged in the SQL Server Errorlog file:
<Date Time> <spid number> Error: 3314, Severity: 21, State: 4.<Date Time> <spid number> During undoing of a logged operation in database '<database>', an error occurred at log record ID (293790:15039:64). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.<Date Time> <spid number> Database <database> was shutdown due to error 5242 in routine 'XdesRMReadWrite::RollbackToLsn'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.<Date Time> <spid number> Error: 9001, Severity: 21, State: 1.<Date Time> <spid number> The log for database '<database>' is not available. Check the event log for related error messages. Resolve any errors and restart the database.<Date Time> <spid number> Error: 9001, Severity: 21, State: 1.<Date Time> <spid number> The log for database '<database>' is not available. Check the event log for related error messages. Resolve any errors and restart the database.<Date Time> <spid number> Error: 9001, Severity: 21, State: 5.
Additionally, a mini-dump file is generated in the SQL Server log folder.If you are running SQL Server 2008 R2, you must install Cumulative update 7 for SQL Server 2008 R2 RTM or Cumulative Update package 1 for SQL Server 2008 R2 SP1 to resolve this issue. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2504090 FIX: Access violation when you insert data into a new partition of a partitioned table after you drop a column of the table in SQL Server 2008 R2 Note Hotfix 2504090 addresses different symptoms that occur for the same reasons as for this issue. Therefore, you may also encounter the symptoms that are mentioned in the article for hotfix 2504090.
Cause
This issue occurs because the accessor that SQL Server uses to insert data into different partitions recognizes the metadata changes incorrectly. When data is inserted into a new partition that is created after a column is dropped, the maximum number of nullable columns for the new partition might be one less than the number that was for the old partition.
Resolution
Cumulative update information
SQL Server 2008 Service Pack 1
The fix for this issue was first released in Cumulative Update 15 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2555406 Cumulative update package 15 for SQL Server 2008 Service Pack 1Note 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:
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 SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. 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 Service Pack 2
The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2527180 Cumulative update package 4 for SQL Server 2008 Service Pack 2Note 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:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Workaround
To work around this issue, rebuild all partitions of the partitioned table after you drop one of its columns. Note This issue may reoccur when a new column is dropped and a new partition is created if this hotfix is not installed.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
In SQL Server 2008 Service Pack 3 the assertion "sourceColumnCount <= maxNullableColumn" (in CDRecord.cpp) was enabled in retail builds to catch the error condition earlier. Note that a SQL Server running a version with the above fix (or higher) can also encounter one of the symptoms when it has loaded a database from a previous build of SQL Server. In this case, you need to rebuild all partitions of the affected partitioned tables once to correct the wrong metadata.
References
For more information about data compression, visit the following MSDN website:
General information about data compressionFor more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problemsFor more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
