Microsoft distributes Microsoft SQL Server 2008 Service Pack 2 (SP2) and Microsoft SQL Server 2008 Service Pack 3 (SP3) 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 Service Pack 2 (SP2) and Microsoft SQL Server 2008 Service Pack 3 (SP3) fix release.
Symptoms
Consider the following scenario:
-
You have a database that has a name whose length nearly reaches the name-length limit in a Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2 instance.Note The length of a SQL Server 2008 or SQL Server 2008 R2 database name has a limit of 123 characters.
-
You perform some operations on the database. These operations could cause some events to be logged in the Windows Application log.
In this scenario, event ID 322 together with the following message is logged unexpectedly in the Windows Application log and in the SQL Server Agent error log, even though the operations are completed successfully:
The data portion of event 8957 from MSSQL$MS2008 is invalid.
You expect only the events that are described in the "Symptoms" section to logged in the Windows Application log, and not event ID 322 or the error message.For example, if you run the DBCC CHECKDB statement on a database, an event that resembles the following should be logged in the Windows Application log:However, the event ID 322 error is logged in the Windows Application log and in the SQL Server Agent error log.
Cause
This issue occurs because an incorrect value is set for a constant that is used to calculate the length of event data.
Resolution
Cumulative update information
SQL Server 2008 R2 Service Pack 2
The fix for this issue was first released in Cumulative Update 2 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:
2740411 Cumulative Update package 2 for SQL Server 2008 R2 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 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 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released
SQL Server 2008 R2 Service Pack 1
The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2723743 Cumulative update package 8 for SQL Server 2008 R2 SP1Note 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 Service Pack 1 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 SP1 was released
Cumulative update package 6 for SQL Server 2008 SP3
The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008 SP3, click the following article number to view the article in the Microsoft Knowledge Base:
2715953 Cumulative update package 6 for SQL Server 2008 Service Pack 3Note 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 SP3 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:
2629969 SQL Server 2008 builds that were released after SQL Server 2008 SP3 was released
Cumulative update package 11 for SQL Server 2008 SP2
The fix for this issue was first released in Cumulative Update 11. For more information about how to obtain this cumulative update package for SQL Server 2008 for SQL Server 2008 SP2, click the following article number to view the article in the Microsoft Knowledge Base:
2715951 Cumulative update package 11 for SQL Server 2008 SP2 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 for SQL Server 2008 SP2 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:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
