Our weekly integrity check job on one of our servers has now failed two weeks in a row. In both cases, the only database known to be generating an error is the 'master' db.
If I run the DBCC CHECKDB('master') command manually, I get the same results. The log shows no errors, and that the DB is A-OK. The output to the console of the command indicates the same. However, instead of the final line about errors reported by DBCC (as you see here, when I run the command against msdb):
CHECKDB found 0 allocation errors and 0 consistency errors in database 'msdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
I get Msg 0:
CHECKDB found 0 allocation errors and 0 consistency errors in database 'master'.
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Naturally, as it appears the results that should be discarded are the ones that say the DB is fine, I'm in a bit of a quandary.
The database has not been restarted since I first saw the error; I'll be requesting one today.
The databases on the server all seem to be behaving normally.
Our external DBA team has recommended updating the server (SQL 2008, SP2, version 10.00.4279) to SP2 cumulative update 7, as that is supposed to fix a situation where you get this message running DBCC CHECKDB on a DB/table with a spatial index. While I don't mind updating (I'd actually have them go to SP3, CU3), this looks like a "hail Mary" play to me.
1. Is it likely that I actually have a corrupt DB?
2. Noting that we'd install the CU on two other servers that have no symptoms before we'd get to the production box that does - does it seem at all likely that SP2CU7 (or SP3CU3) will actually fix the problem?
3. Is there something else I should be looking at/checking on?
Thanks in advance for your advice.
R David Francis