Viewing 15 posts - 841 through 855 (of 994 total)
Simple answer - no. You need to attach the database and then run repair (as you don't have a backup). Are you having problems attaching the database?
A torn-page is basically...
November 28, 2007 at 11:18 am
You can't interrupt a query that's rolling back. You have two options:
1) change the query so it doesn't 'crash'. What do you mean by that?
2) break up the operation into...
November 27, 2007 at 5:55 pm
GURAY (11/23/2007)
If your datas or backups corrupted you can repair them with Nucleus Sql Recovery program. http://www.nucleustechnologies.com
Be careful. As with all such software, it can only *try* to repair...
November 27, 2007 at 5:52 pm
Hi Carl,
The pages and extents that are deallocated by the TRUNCATE are locked until the transaction commits or rolls back so that no other transaction can allocate and overwrite them....
November 27, 2007 at 5:19 pm
Hi Steve,
This is a corrupt page at the leaf-level of the clustered index for sysindexes. It's not repairable by DBCC (or any other documented or undocumented means). The only options...
November 17, 2007 at 12:47 am
I'm intrigued - can you post the T-SQL you're using? I'm not a stats expert but I can probably get Kimberly to take a look.
Yes, if you're doing index rebuilds...
November 14, 2007 at 10:07 pm
No problem.
Nope - what I posted is what I would do in this situation.
Thanks
November 14, 2007 at 3:24 pm
You need to use T3604, not T3406.
The data in the repaired database will not be available. The page that had the 823 error cannot be read by the operating system...
November 14, 2007 at 2:43 pm
Well, you've certainly got some IO susbsystem-caused corruption in there. You could *try* rebuilding the clustered index on the COSP table to fix some of the problems, but the rest...
November 14, 2007 at 2:15 pm
You need to post the complete output before I can tell you what the problems are - then it *may* be possible to get around the problems without running repair....
November 14, 2007 at 12:24 pm
Pretty simple:
Header corruptions (and all other types of page corruption) are almost always caused by IO subsystem issues.
The best ways to prepare are:
1) have a sound backup strategy
2) if need...
November 14, 2007 at 12:07 pm
Nope - you can only trap the last error returned. Same with corruption errors reported by CHCEKDB.
November 14, 2007 at 4:45 am
Hi Ali,
You do need to run DBCC CHECKDB. Beware that even if CHECKDB finds corruptions, it will complete successfully, Depending on how your maintenance job is setup, you may miss...
November 14, 2007 at 4:29 am
"data is very more important than structure."
Absolutely - so if you have important data then you should have a sound backup strategy and even a redundant mirror of the data....
November 10, 2007 at 11:28 am
Sigh - no, I'm not wrong. If an MDF's file header is corrupt, it nearly always means that a lot of the rest of the database has corruptions too. No...
November 8, 2007 at 6:50 pm
Viewing 15 posts - 841 through 855 (of 994 total)