Article ID: 981611 - Last Review: June 23, 2010 - Revision: 2.0 FIX: An access violation occurs when you use the COUNT_BIG function and the OVER clause in a query in SQL Server 2008 or 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 fixes that were included with the previous SQL Server 2008 or SQL Server 2008 R2 fix release. On This PageSYMPTOMSIn 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. SOURCE: MSSQLSERVER Event ID: 17310 Message: 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. <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. RESOLUTIONCumulative update informationSQL Server 2008 R2The 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
(http://support.microsoft.com/kb/2072493/
)
Cumulative update package 2 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 SQL Server 2008The 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
(http://support.microsoft.com/kb/981702/LN/
)
Cumulative update package 8 for SQL Server 2008 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 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
(http://support.microsoft.com/kb/970365/LN/
)
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.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. REFERENCESFor information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For 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
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates APPLIES TO
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
