Viewing 15 posts - 136 through 150 (of 994 total)
moosamca (1/24/2011)
The SQL Server 2005 some time through this error, but i don't know why it is coming. However the database will attach successfully, even though it showed...
January 24, 2011 at 4:17 pm
moosamca (1/24/2011)
Hi,Did you tried DBCC CHECKTable with Repair_rebuild?
Regards
Moosa
It's great that you're enthusiastic - but please don't post advice when you don't know what you're talking about. You cannot repair...
January 24, 2011 at 4:17 pm
moosamca (1/24/2011)
Hi Bodsda ,Hope you have the backup already. Please try with DBCC CHECKDB with repair_allow_data_loss. Hope this will help to resolve.
Regards
Moosa
It's great that you're enthusiastic - but please...
January 24, 2011 at 4:16 pm
CHECKCATALOG on 2000 was very basic - that's why it was rewritten and I included it in CHECKDB.
January 24, 2011 at 2:23 pm
It's a bummer when companies don't recognize the value of training and the ROI they'll get - I hear you.
January 10, 2011 at 1:51 pm
Take each of the errors like
Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10088548), slot 0, text ID 312662884352 is not referenced.
And use DBCC PAGE...
January 5, 2011 at 7:23 am
The corruption was transient - i.e. it was the SAN returning bad data when the data was really good on disk. Subsequent read worked. This is not uncommon.
January 5, 2011 at 7:12 am
Gail asked me to offer advice.
It's log corruption on disk (or potentially from a memory scribbler - hopefully the former).
If I was on the system, I'd do the following to...
January 5, 2011 at 6:39 am
We may be daft, but we're not *that* daft 🙂
December 27, 2010 at 12:04 pm
The vast majority of the time I try to be very supportive when giving constructive criticism, but sometimes if the person *repeatedly* posts incorrect things, a harsh wake-up call is...
December 22, 2010 at 6:14 am
Ask them to be specific. Maybe mention you're talking to me and I'll be discussing the case with Bob Ward. 🙂
December 1, 2010 at 8:43 pm
Hmm. Anything that causes stats corruption is a bug in SQL Server. Did they mean some SQL query is causing the corruption? Are they investigating the bug? This sounds very...
November 30, 2010 at 2:24 pm
Absolutely.
To clarify what Gail said, tempdb should also be checked, but CHECKDB runs very differently on tempdb so it doesn't all get checked. This is because the underlying mechanism CHECKDB...
November 30, 2010 at 8:55 am
Ah - so it doesn't say "some of your processes from the front end application has corrupted the statistics" like you said. I'm surprised they didn't speculate on how the...
November 29, 2010 at 5:40 pm
Viewing 15 posts - 136 through 150 (of 994 total)