Viewing 15 posts - 34,021 through 34,035 (of 49,552 total)
WayneS (2/14/2010)
At least he seems to be trying things out in Dev first... IMO, a good sign.
Oh definitely.
It wasn't the testing out that bugged me. It was asking how...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 10:06 am
Mh-397891 (2/14/2010)
Thanks for your quick responses.No, I am not ignoring what you are saying, since I am testing in development so I wanted to try the last option of repair_data_loss.
The...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 9:34 am
Alvin Ramard (2/14/2010)
GilaMonster (2/14/2010)
Maybe I should answer corruption questions in Minbari or Vulcan from now on...http://www.sqlservercentral.com/Forums/Topic865038-146-1.aspx
It's worth a try.
You might want to make one change to your answer: "Get out...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 9:34 am
Maybe I should answer corruption questions in Minbari or Vulcan from now on...
http://www.sqlservercentral.com/Forums/Topic865038-146-1.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 9:05 am
Are you completely ignoring everything I'm saying?
This error is not repairable. CheckDB will not fix it. Get out your latest backup and restore the database from backup.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 9:00 am
Those disk stats don't look too bad. sec/read is a little high, sec/write slightly high.
You say that you think the problems come from 2 frequently accessed tables.... If a table...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 7:32 am
Some traceflags are documented in Books online, some are mentioned in kb articles, many are completely undocumented. I don't think there's a list anywhere.
What problem are you trying to solve...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 7:25 am
You've got damage to the allocation structures in this database. It's bad enough that CheckDB can't even check the entire database because it can't tell how things are supposed to...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 7:15 am
Mh-397891 (2/14/2010)
How do I find where the problem is? which will help me to fix the errors.
There is damage to the system tables in this database. Specifically sysallocunits. This damage...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 7:11 am
The index name is in the column called name in sys.indexes. Just add it to the select clause
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 1:32 am
Please post table definitions, index definitions and execution plan, as per http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 1:31 am
CirquedeSQLeil (2/13/2010)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 14, 2010 at 1:29 am
Steve Jones - Editor (2/13/2010)
I would also dig into your hardware and make sure you do not have an underlying problem there
Yup. Absolutely. Something damaged the log file's header....
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 13, 2010 at 10:16 am
Please post new questions in a new thread. Your question is totally unrelated to the discussion on this thread.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 13, 2010 at 9:37 am
Restore your latest backup and all transaction log backups up to the point that the DB went suspect.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 13, 2010 at 9:36 am
Viewing 15 posts - 34,021 through 34,035 (of 49,552 total)