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 |
rob_garcia
Starting Member
1 Post |
Posted - 2007-09-03 : 19:58:44
|
I have a SQL Database (150 gb), Some table are corrupted. I ran the command DBCC CHECKTABLE for 1 table the most important table in my system, but this command delays 50 hours and still running.Is there something I can do to do it faster?what else can I do? |
|
Zoroaster
Aged Yak Warrior
702 Posts |
Posted - 2007-09-03 : 20:02:32
|
quote: Originally posted by rob_garcia I have a SQL Database (150 gb), Some table are corrupted. I ran the command DBCC CHECKTABLE for 1 table the most important table in my system, but this command delays 50 hours and still running.Is there something I can do to do it faster?what else can I do?
What version of SQL Server? You can specify physical only which will reduce the overhead. ------------------------Future guru in the making. |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-09-03 : 21:41:12
|
Double check with 'sp_who2 active', maybe it's blocked by other processes. |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2007-09-04 : 02:26:24
|
It's probably doing a 'deep-dive' check - its found some corruption and its going back to work out exactly what the corruption is. Is there any disk/cpu activity?Paul RandalManaging Director, SQLskills.com |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-09-04 : 03:59:19
|
Well, I reckon you need to get everyone off the database so you can check it, and repair it if that is appropriate.Otherwise restore from backup.Kristen |
|
|
|
|
|