December 6, 2004 at 11:06 am
I have a DB on my SQL Server 2000 Cluster with what I think is a corrupt table.
They cannot access the table from their access frontend, and when I attempt to open the table from Enterprise Manager, I get the same error that they are getting from the Front-end: Microsoft - odbc sql server device drive - timeout expired
I'm thinking I have some corrupt data in this table and wondering if there is a way to repair or check it?? or the best way to recover this data from a backup?????
December 6, 2004 at 11:25 am
Is there a rollback or something else that is sucking the memory off the server?
I would start with sp_who2 and go from there. It may be a long running query/statement, something crashed on the server (check it's desktop)
Try double-clicking on the table and then look at sp_who2 and find you and you may see blocking....
Good Hunting!
AJ Ahrens
webmaster@kritter.net
December 6, 2004 at 11:26 am
if that doesn't help then you can have a look at DBCC CHECKTABLE (but I never used it so I can't provide much info).
December 6, 2004 at 11:42 am
It sound like you have connection issues. Try login in the server see whether you can select the table.
December 6, 2004 at 11:44 am
looks like I have a long running process.. dbcc check database from sa against the database that is having a problem. !! not sure how long this has been running. How can I kill this? or should I kill it?????
December 6, 2004 at 11:47 am
run "dbcc inputbuffer(your_long_running_process_spid)" and post the result back.
December 6, 2004 at 12:39 pm
I killed the process and I am going to schedule a failover of the Cluster so I can stop and restart SQL Server Instance. Thank you for the Help!!!
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply