Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
madhukar_kcreddy
Starting Member
2 Posts |
 Posted - 2008-03-24 : 08:42:55
|
| as |
|
|
manlmm
Starting Member
1 Post |
Posted - 2008-03-27 : 03:52:31
|
| Hi, Even we had faced the same problem, You can find out the index name based on the Index ID and Table name(which is throwing error),Reindex the Table and check. |
 |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2008-03-27 : 20:10:17
|
| I don't believe that will work in this case - from the inital latch failure messages it seems you've got something physically wrong with the disk where this database resides - the IOs can't complete properly.Also, the errors don't just pertain to a non-clustered index - there's a clustered index in there too.My suggestions: - start taking backups - export the data out to a new database, or if this isn't palatable, run repair - but that's going to cause data loss. - whichever you choose, run diagnostics on your IO subsystem to flush out any hardware/software issues you may have.ThanksPaul RandalManaging Director, SQLskills.com |
|
|
|
elancaster
A very urgent SQL Yakette
1208 Posts |
Posted - 2008-04-04 : 04:28:12
|
quote:
Originally posted by madhukar_kcreddy
as
grr.... why why why???Em |
|
|
|
|
|
|
as