I am struggling with some databases going inconsistent.
We are running SQL 2000 MSDE on NT 5.2. The db's (most of the times is only one of them but at times others join the party) generate the following error:
A possible database consistency problem has been detected on database 'xx'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on database 'xx'.
Obviously DBCC doesn't detect any errors. I checked the disks and the RAM but no errors there either. We have other server running 2005 and 2008 and they are fine so far.
So now I am stuck with sql dumps which are generated every now and then. I have no idea what to do with them, the sql code that is 'dumped' is always different so I can't even match the failure with a specific action... And anyway I don't understand how some code can randomly make a db incosistent.
Is there anything else I can do other than helplessly hand over the problem to MS ? (which I can't afford).
I read in a post that a guy rebuild all his indexes and that saved the problem but it sounds like pure luck to me (rebuilding them maybe just moved them away from the bad sectors and he had io problems). I will try that too because i'm desperate.