After running the command dbcc checkdb, which is part of a weekly job the following returned
CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2).
Any ideas on how to fixed this sysindexes table.
I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdb
Considering it is sysindexes, my guess you are in for a restore. If that isn't convenient, opening a case with
MS is probably a good idea (but chances are that they don't have better options either). General
recommendations for corrupt or suspect databases: http://www.karaszi.com/sqlserver/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Stephen" <stephen.hoye@.tabq.com.au> wrote in message
news:89575553-91E2-459B-B6CD-0709E5C79463@.microsoft.com...
> After running the command dbcc checkdb, which is part of a weekly job the following returned
> CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2).
> Any ideas on how to fixed this sysindexes table.
> I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdb
>
|||I'm going to create a DTS package and move the database over to anthor DB.
Then I'l rename them. We do have back up, but the problem was picked up after I long weekend.
There was no going back because a number of days had pasted.
Doing the above DTS method, there is no loss in data.
Showing posts with label consistency. Show all posts
Showing posts with label consistency. Show all posts
Tuesday, February 14, 2012
Corrupted sysindexes
Labels:
allocation,
checkdb,
command,
consistency,
corrupted,
database,
dbcc,
errors,
following,
job,
microsoft,
mysql,
oracle,
returnedcheckdb,
running,
server,
sql,
sysindexes,
weekly
Corrupted sysindexes
After running the command dbcc checkdb, which is part of a weekly job the following returne
CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2)
Any ideas on how to fixed this sysindexes table.
I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdConsidering it is sysindexes, my guess you are in for a restore. If that isn't convenient, opening a case with
MS is probably a good idea (but chances are that they don't have better options either). General
recommendations for corrupt or suspect databases: http://www.karaszi.com/sqlserver/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Stephen" <stephen.hoye@.tabq.com.au> wrote in message
news:89575553-91E2-459B-B6CD-0709E5C79463@.microsoft.com...
> After running the command dbcc checkdb, which is part of a weekly job the following returned
> CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2).
> Any ideas on how to fixed this sysindexes table.
> I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdb
>|||I'm going to create a DTS package and move the database over to anthor DB
Then I'l rename them. We do have back up, but the problem was picked up after I long weekend
There was no going back because a number of days had pasted
Doing the above DTS method, there is no loss in data.
CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2)
Any ideas on how to fixed this sysindexes table.
I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdConsidering it is sysindexes, my guess you are in for a restore. If that isn't convenient, opening a case with
MS is probably a good idea (but chances are that they don't have better options either). General
recommendations for corrupt or suspect databases: http://www.karaszi.com/sqlserver/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Stephen" <stephen.hoye@.tabq.com.au> wrote in message
news:89575553-91E2-459B-B6CD-0709E5C79463@.microsoft.com...
> After running the command dbcc checkdb, which is part of a weekly job the following returned
> CHECKDB found 1 allocation errors and 957 consistency errors in table 'sysindexes' (object ID 2).
> Any ideas on how to fixed this sysindexes table.
> I've run dbcc updateusage, dbbc reindex on all tables, dbbc checkdb
>|||I'm going to create a DTS package and move the database over to anthor DB
Then I'l rename them. We do have back up, but the problem was picked up after I long weekend
There was no going back because a number of days had pasted
Doing the above DTS method, there is no loss in data.
Subscribe to:
Posts (Atom)