SQL Server database has corruption, but displays no errors We have an extensive database of tables. I moved over a table from our dev db to our production db using a program called SQL Compare. I just copy paste the SQL it produces into Management Studio and execute it there. Then when I tried to select from the table, it would just keep executing. It is an extremely simple table: two columns, both int, no rows at the moment. We were also unable to delete the table.

We suspect there is some type of corruption, but when we run error checking on tables or database it says there are no problems. I've included our version below, just a SQL Server 2008 R2 Express version. The only errors we get are when we run dbcc checkdb. But it only shows an error on the last line. It shows no errors on any individual tables.

We restarted the SQL Server and then we were able to delete the table. We can select from every table, and everything is now working normal.  But we still have that error at the end of checkdb.

Not sure what to do, it's a little weird. Everything is working, but we are a little afraid something might happen.  We have backups and everything, just trying to fix this if at all possible.

Last lines of checkdb:


  CHECKDB found 0 allocation errors and 0 consistency errors in database '....'.  
  
  Msg 0, Level 11, State 0, Line 0
  A severe error occurred on the current command.  The results, if any, should be discarded.
  
  Msg 0, Level 20, State 0, Line 0
  A severe error occurred on the current command.  The results, if any, should be discarded.


When we run checkdb on another db:


  CHECKDB found 0 allocation errors and 0 consistency errors in database '....' .
  
  DBCC execution completed. If DBCC printed error messages, contact your system administrator.


Our SQL Server database version:

Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (Intel X86)   
Jun 17 2011 00:57:23   
Copyright (c) Microsoft Corporation  
Express Edition with Advanced Services on Windows NT 6.0 &lt;X86&gt; (Build 6002: Service Pack 2) (Hypervisor)
This might help someone with a similar problem.  There was nothing wrong with the database, we needed to install an update.  A service pack I believe.  Then everything was fine.