DBCC CHECKTABLE

I am trying to attach a database and i get this msg:

Could not find row in sysindexes for database id 11, object id 1, index id 1.

Run DBCC CHECKTABLE on sysindexes

i dont know what dbcc checktable is or how to run.

pls help

This is fully documented in the Books Online.

You might even want to run a DBCC CHECKDB to make sure everything is alright.

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||i ran DBCC CHECKDB on master and model and have no problems

I looked at bol for checktable and dont understand, i have not worked with SQL Srv or another db before. i dont know how to run on sysindexes as the msg states in the 1st post
how do i run it with REPAIR_ALLOW_DATA_LOSS , REPAIR_FAST or REPAIR_REBUILD
here is the whole msg:

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'BUSTED'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Could not find row in sysindexes for database ID 11, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
Could not open new database 'Asset5'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 602)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=602&LinkId=20476

BUTTONS:

OK

|||

i think you are trying to attach database from SQL Server 2005 to SQL Server 2000 which is not possible. Please check the version of source and target. If its from 2005 to 2000 then its not possible.

Madhu

|||

For the source database that you are trying to attach, run DBCC CHECKDB on that database. You need to check and see if the database you are trying to attach is corrupted. You would do that by executing the DBCC on the source database, not on the server you are trying to attach to.

Log onto the server where the source database is and change the database context to that database. Then execute

DBCC CHECKDB

You don't want to run with repair options to start with - you just want to do a checkdb first with no repair options and go from there. Using the repair allow data loss option isn't something you generally want to do anyway. There are other options before going down that road that should be explored. It all depends on what messages are returned when you do the DBCC CHECKDB

-Sue