Running: SQL Server R2 SP1 version 10.50.2500.0
I have an odd error that just happened on my SQL Server and cannot see that a Cumulative Update fixes the issue. I am cautious on installing Cumulative Updates so I don't want to just install unless something does fix an issue.
The error I received in the SQL Server Error Log is as follows:
2012-10-04 22:54:53.50 spid109 Error: 17065, Severity: 16, State: 1.
2012-10-04 22:54:53.50 spid109 SQL Server Assertion: File: <kglobal.cpp>, line = 349 Failed Assertion = '!"Arithmetic operation failed"' Operands: 0xfffffffec0a9ece0, 0x0; HRESULT: 0x80070216. This error may be timing-related. If the error
persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
2012-10-04 22:54:53.51 spid109 Error: 3624, Severity: 20, State: 1.
2012-10-04 22:54:53.51 spid109 A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running
DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
2012-10-05 00:00:45.81 spid23s This instance of SQL Server has been using a process ID of 1424 since 9/13/2012 1:28:50 AM (local) 9/13/2012 7:28:50 AM (UTC). This is an informational message only; no user action is required.
I have ran DBCC CHECKDB on the database where the offending query was and there was no issue found, the database checked out fine. Database continues to perform and work.
Does anyone know what may be causing the issue and/or if the problem is address in a Cumulative Update for SQL Server R2 SP1. I have already looked through the Cumulative Update list of fixes and nothing seems to address it.
Thanks,
Sean