SQL Server Performance

Error: Could not find row in sysindexes for database. 8966, 823 and 602

Discussion in 'Other SQL Server Blogs around the Web' started by Anonymous, Aug 14, 2007.

  1. Anonymous New Member

    Long ago, not long ago.... No doubt that many of you might have gone through the error above within your SQL environment, also I see many forum posts out there to resolve the issue. The bottom line of this issue is Hardware and no other issue can contribute such a problem. So this is where DBA's role is enhanced to take care of SQL Server hardware too. By going further into details recently System Operations &amp; Developers complained about error they are receiving whenever tried to select data...(<a href="http://sqlserver-qa.net/blogs/tools/archive/2007/08/14/error-could-not-find-row-in-sysindexes-for-database-8966-823-and-602.aspx">read more</a>)<img src="http://sqlserver-qa.net/aggbug.aspx?PostID=1402" width="1" height="1">
  2. johndisuza New Member

    The error 8966 is encountered in SQL Server when the DBCC CHECKDB command fails to repair the corrupt or damages SQL database. The occurence of the error is a clear indication that the corruption is severe and you need to use an expert tool to get rid of the error. Use a reliable tool to repair SQL database and access the data that has become inaccessible.
  3. satya Moderator

    Appreciate your comment on the post, I'm sure for the review of your tool which is related to SQL Server it is ideal if you can get in touch with Webmaster and get the reviews up.

Share This Page