Applies ToSQL Server 2008 R2 Service Pack 2 SQL Server 2008 R2 SQL Server 2008

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 fixes that were included with the previous SQL Server 2008 or SQL Server 2008 R2 fix release.

Symptoms

In Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2, an access violation occurs when you run a query that uses the COUNT_BIG function followed by the OVER clause. Additionally, you receive the following error message:

Msg 0, Level 11, State 0, Line <line>A severe error occurred on the current command. The results, if any, should be discarded.Msg 0, Level 20, State 0, Line <line>A severe error occurred on the current command. The results, if any, should be discarded.

Additionally, the following event is logged in the Application log:

SOURCE: MSSQLSERVEREvent ID: 17310Message: A user request from the session with SPID <ID> generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.

When this problem occurs, a mini-dump file is generated in the SQL Server log folder. Additionally, an error message that resembles the following is logged in the SQL Server log file:

<Date Time> spid<ID> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION<Date Time> spid<ID> * Access Violation occurred reading address 0000000000000010<Date Time> spid<ID> <removed><Date Time> Server Error: 17310, Severity: 20, State: 1.<Date Time> Server A user request from the session with SPID <ID> generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.

Resolution

Cumulative update information

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 2. 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:

2072493 Cumulative update package 2 for SQL Server 2008 R2Note 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

The fix for this issue was first released in Cumulative Update 8 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:

981702 Cumulative update package 8 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. 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:

970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedMicrosoft 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.

Status

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

References

For 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:

822499New 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

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.