Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / September 2008

Tip: Looking for answers? Try searching our database.

Database error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
DCR - 30 Sep 2008 19:22 GMT
When I run the check database command, I get this error:
error -2147212552: Table error: database 'rivers', index
'timecard.IX_cashier'(ID 1237579447)(index ID 2). extra or invalid key for
the keys:

Does anybody know how to fix this?
Thanks
Dave
Kalen Delaney - 30 Sep 2008 19:29 GMT
Hi Dave

Is this the only error? If so, and since it is referring to an index, can
you try just dropping and rebuilding the index?

Signature

HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
www.SQLTuners.com

> When I run the check database command, I get this error:
> error -2147212552: Table error: database 'rivers', index
[quoted text clipped - 4 lines]
> Thanks
> Dave
DCR - 30 Sep 2008 20:05 GMT
I've re-index the database. It didn't fix the problem. What do you mean
dropping?

> Hi Dave
>
[quoted text clipped - 9 lines]
> > Thanks
> > Dave
Eric Isaacs - 30 Sep 2008 20:22 GMT
It sounds like a corrupt index.  Drop (delete) the index(es) on the
table and recreate it (them.)

-Eric Isaacs
Kalen Delaney - 30 Sep 2008 20:29 GMT
Hi Dave

What do you mean by re-index the database? How did you do that?

Please check the documentation for the DROP INDEX command.  After you drop
the index you should rebuild it with CREATE INDEX.
(Sometimes these two steps can be combined, but since we trying to get rid
of corruption, it's best to do them separately.)

Signature

HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
www.SQLTuners.com

> I've re-index the database. It didn't fix the problem. What do you mean
> dropping?
[quoted text clipped - 13 lines]
>> > Thanks
>> > Dave
Eric Isaacs - 30 Sep 2008 22:14 GMT
Kalen,

Are you wondering what reindexing is, or what DCR's definition of
reindexing is?

Reindexing is different than drop and recreate.  Many times it's more
efficient to reindex than drop and recreate, but if you have a corrupt
index, dropping it and recreating it is probably the best way to go,
especially if you tried to reindex it and it was still corrupted.

http://blog.sqlauthority.com/2007/01/31/sql-server-reindexing-database-tables-an
d-update-statistics-on-tables/


-Eric Isaacs
Kalen Delaney - 30 Sep 2008 22:27 GMT
I'm wondering what DCR meant by reindexing and how he did it.
And I did mention that for fixing corruption, drop + create was probably
best. I am well aware of the differences.
Signature

HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
www.SQLTuners.com

> Kalen,
>
[quoted text clipped - 9 lines]
>
> -Eric Isaacs
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.