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 |
|
rangerbud249
Starting Member
3 Posts |
 Posted - 2005-08-12 : 15:56:27
|
| I have a db that is about 50Gigs. Last night it went into a suspect mode and I have not been able to get any of my tables to display. I am running the dbcc checkdb. I have been running it for over 7 hrs. Do you have any suggestions as to what I should do or do you have any ideas as to how long this process might take?thanks, |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-08-12 : 16:06:14
|
| You need to let the CHECKDB complete and then post the results.Lots of questions for you:What's the machine config (memory, #cpus, cpu type, IO system and capabilities)Do you have any concurrent activity on the database (I'm guessing not)Are there any dumps in the LOG directory?Any clues in the errorlog at the time the DB went suspect?Is there any evidence of hardware problems in the errorlog or Windows event logs?Do you have write-caching enabled?ThanksPaul RandalDev Lead, Microsoft SQL Server Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
 |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-08-12 : 16:08:39
|
| A CHECKDB of a 50gig DB with no errors on a decent box shouldn't take more than an hour. However, I suspect its found a bunch of corruption resulting in mis-matched indexes and so its gone back to do deep cross-checks of the non-clustered indexes to figure out which rows are missing - this takes a lot of time.Paul RandalDev Lead, Microsoft SQL Server Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
|
rangerbud249
Starting Member
3 Posts |
Posted - 2005-08-12 : 16:31:18
|
| We believe this happened because of a power outage last night.Here are the specs.memory = 4Ggs#cpu = 2cpu type = P3IO sys = ArrayedIO capabilities = d: 49Ggs total 43Ggs availableWrite-caching = nowe do have the System event log files and the Application event log files, but they are huge. how do you want me to send them to you?The log that I believe reported the error was this one8/12/2005 2:03:51 AM MSSQL$LIVETVSQL Error (2) 17052 N/A LIVETVSQL Error: 823, Severity: 24, State: 2I/O error (torn page) detected during read at offset 0x000009f4056000 in file 'd:\Program Files\Microsoft SQL Server\MSSQL$LIVETVSQL\data\livetvsql_Data.MDF'.thanks for all your help,jose |
|
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-08-12 : 17:31:03
|
| No thanks - its because of the power outage. Some of the writes in progress at the time didn't complete correctly (you can see that you have at least one torn page).Do you have up-to-date backups? Its probably quicker to just restore from them as you know now that the cause was the power outage and not bad hardware.Paul RandalDev Lead, Microsoft SQL Server Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
|
|
|
|
|
|
dbcc checkdb ?