I've run into a very strange and frustrating recurring error.
I have a Single instance SQL Server 2005 DBMS on Win2K3 Server x86. The problem occurs with a *single* database on the system, the other databases are unaffected. We primarily access this database for editing through an Access 2007 data project,
though it's accessed (select only) from many places using odbc or oledb.
Basically some sort of corruption (or apparent corruption) occurs after a server update and reboot (usually unrelated to the DB software). After that, the database is fine sometimes, other times it is fine until we try to access it via the ADP.
At that point it becomes inaccesssible by the ADP, though it can still be accessed through all other methods. Running DBCC CHECKDB (databasename) returns:
Msg 211, Level 23, State 51, Line 1 Possible schema corruption. Run DBCC CHECKCATALOG.
Running DBCC CHECKCATALOG (databasename) returns no errors.
Restarting the database service (from inside SSMS typically) will fix it *eventually* after a few restarts. I can find no rhyme or reason to the apparent corruption. I'll be glad to look and post any other log entries that might be relevant.
I should note that the database was originally created way back in SQL Server 7, though it's got no real customizations, triggers, and very few constraints on it. It's
View Complete Post