I keep receiving his error every Monday, after my Sunday's Integrity job schedule
"DBCC CHECKDB WITH NO_INFOMSGS " failed with the following error: "Database 'xxxxxxxxxxx' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. A severe error occurred on the current command. The results, if any, should be discarded.". Possible failure reasons: Problems w... The package execution fa... The step failed.
1st time the job ran, it went ok. After that, it started failing.
The database is not in suspect state. It is up and running.I actually ran a DBCC myself, not via job, and gave no errors; but that does not mean it is not corrupted, still it can be.
This is the only database on same server and drive that it is failing the Integrity job. And the Server Admin states there is no server or disk problem.
Here's the SQL version:
Microsoft SQL Server 2005 - 9.00.4053.00 (X64) May 26 2009 14:13:01 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.0 (Build 6001: Service Pack 1)
Yeah, I know, old stuff, but no plans to upgrade that to Denali or SQL2008 soon... :-( ... it is what it is ...