August 14, 2008 at 7:36 am
I run dbcc checkdb and received this error
CHECKDB found 2 allocation errors and 2 consistency errors in table 'ALLOCATION' (object ID 99).
And there is no such table in the database.
Any ideas????
¤ §unshine ¤
August 14, 2008 at 7:58 am
Can you post the exact text? This might be a system table/area.
If you are getting errors, they are almost always hardware related. If this is a production system, I wouldn't mess around at all and would call Microsoft support for help with this.
August 14, 2008 at 8:02 am
This is the exact text
CHECKDB found 2 allocation errors and 2 consistency errors in table 'ALLOCATION' (object ID 99).
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
¤ §unshine ¤
August 14, 2008 at 8:31 am
That's refering to the allocation pages (GAM, SGAM, PFS). They're not actually objects, but they say which pages in the files are used, available and how much space on them. If those are corrupt, you have a problem.
Can you post the full output of
DBCC CHECKDB (< Database name > ) WITH NO_INFOMSGS
Got a 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
August 14, 2008 at 8:34 am
No good backup, this db has been corrupt for quite some time, i'm trying to fix what i can with what i have.
this is the output with no info and all error
Nonqualified transactions are being rolled back. Estimated rollback completion: 100%.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2729420). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2729421). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2729422). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2892701). The PageId in the page header = (0:8).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2892702). The PageId in the page header = (0:8).
Server: Msg 2515, Level 16, State 1, Line 1
Page (1:12472664), object ID 6, index ID 0 has been modified but is not marked modified in the differential backup bitmap.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 99, index ID 0, page (1:12269574). Test (m_slots[0].GetOffset () == PAGEHEADSIZE) failed. Values are 0 and 96.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 99, index ID 0, page (1:12269574). Test (Align(m_slots[-1].GetOffset ()) == Align(m_slots[0].GetOffset () + sizeof(GAMHEADER) + sizeof(DataRecHdr))) failed. Values are 96 and 94.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 99, index ID 0, page (1:12269574). Test (m_slots[0].GetOffset () == PAGEHEADSIZE) failed. Values are 0 and 96.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 99, index ID 0, page (1:12269574). Test (Align(m_slots[-1].GetOffset ()) == Align(m_slots[0].GetOffset () + sizeof(GAMHEADER) + sizeof(DataRecHdr))) failed. Values are 96 and 94.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 299864135, index ID 0: Page (1:10224670) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 299864135, index ID 0, page (1:10224670). Test (sorted .offset >= PAGEHEADSIZE) failed. Slot 45, offset 0x1 is invalid.
Server: Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 299864135, index ID 0, page (1:10224670). Test (sorted.offset >= max) failed. Slot 0, offset 0x2d overlaps with the prior row.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 299864135, index ID 1. Page (1:10224669) is missing a reference from previous page (1:10224670). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 299864135, index ID 1. Page (1:10224670) was not seen in the scan although its parent (1:10224456) and previous (1:10224671) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 411148510, index ID 0: Page (1:2005832) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 0, page (1:2005832). Test (sorted .offset >= PAGEHEADSIZE) failed. Slot 35, offset 0xc is invalid.
Server: Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 0, page (1:2005832). Test (sorted.offset >= max) failed. Slot 0, offset 0x23 overlaps with the prior row.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 411148510, index ID 0: Page (1:5363504) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 411148510, index ID 0: Page (1:5627224) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 411148510, index ID 0: Page (1:17210894) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 0, page (1:17210894). Test (sorted .offset >= PAGEHEADSIZE) failed. Slot 22, offset 0x1 is invalid.
Server: Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 0, page (1:17210894). Test (sorted.offset >= max) failed. Slot 0, offset 0x16 overlaps with the prior row.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 1. Page (1:2005832) was not seen in the scan although its parent (1:2005871) and previous (1:2005823) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 1. Page (1:2005833) is missing a reference from previous page (1:2005832). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 1. Page (1:5363504) was not seen in the scan although its parent (1:5363597) and previous (1:5363503) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 1. Page (1:5363505) is missing a reference from previous page (1:5363504). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 1. Page (1:5627224) was not seen in the scan although its parent (1:5627512) and previous (1:5627223) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 1. Page (1:5627225) is missing a reference from previous page (1:5627224). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 1. Page (1:17210894) was not seen in the scan although its parent (1:17211215) and previous (1:17210893) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 1. Page (1:17210895) is missing a reference from previous page (1:17210894). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 603865218, index ID 0: Page (1:2729420) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 603865218, index ID 0: Page (1:2729421) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 603865218, index ID 0: Page (1:2729422) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 603865218, index ID 0: Page (1:2892701) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 603865218, index ID 0: Page (1:2892702) could not be processed. See other errors for details.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 603865218, index ID 1. Page (1:2729420) was not seen in the scan although its parent (1:2729492) and previous (1:2729419) refer to it. Check any previous errors.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 0 allocation errors and 5 consistency errors not associated with any single object.
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'syscomments' (object ID 6).
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 2 allocation errors and 2 consistency errors in table 'ALLOCATION' (object ID 99).
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 0 allocation errors and 5 consistency errors in table 'Master1_2007' (object ID 299864135).
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 0 allocation errors and 16 consistency errors in table 'Coll_NumCalls_To_Remove_or_Replace' (object ID 411148510).
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 603865218, index ID 1. Index node page (1:2729492), slot 240 refers to child page (1:2729421) and previous child (1:2729420), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 603865218, index ID 1. Index node page (1:2729492), slot 241 refers to child page (1:2729422) and previous child (1:2729421), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 603865218, index ID 1. Page (1:2729423) is missing a reference from previous page (1:2729422). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 603865218, index ID 1. Page (1:2892701) was not seen in the scan although its parent (1:2892705) and previous (1:2892700) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 603865218, index ID 1. Index node page (1:2892705), slot 308 refers to child page (1:2892702) and previous child (1:2892701), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 603865218, index ID 1. Page (1:2892703) is missing a reference from previous page (1:2892702). Possible chain linkage problem.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 0 allocation errors and 12 consistency errors in table 'Acxiom_Opticx_History' (object ID 603865218).
Server: Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 796650729, index ID 7, page (1:5363504). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1880277295, index ID 0, page (1:5627224). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 796650729)' (object ID 796650729).
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 1880277295)' (object ID 1880277295).
CHECKDB found 2 allocation errors and 43 consistency errors in database 'ArrowProdDB'.
¤ §unshine ¤
August 14, 2008 at 8:40 am
sunshine (8/14/2008)
No good backup, this db has been corrupt for quite some time, i'm trying to fix what i can with what i have.this is the output with no info and all error
The repair level on the DBCC statement caused this repair to be bypassed.
Did you run that with a repair level specified? If so, please run it again with JUST the no_infomsgs and all_errormsgs options.
Also, am I correct in saying this is a SQL 2000 server?
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
August 14, 2008 at 8:46 am
Yes this is a sql server 2000. The above output was with repair_rebuild. I will not be ablet o re-do a repair_rebuild as this is a production db, until late tonight. But I'll run without that now.
¤ §unshine ¤
August 14, 2008 at 8:50 am
sunshine (8/14/2008)
But I'll run without that now.
Please do. I would like to see just the informational output without any comments on repair.
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
August 14, 2008 at 11:49 am
Here it is.. thank you so much for your help... 😀
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2729420). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2729421). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2729422). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2892701). The PageId in the page header = (0:8).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:2892702). The PageId in the page header = (0:8).
Server: Msg 2515, Level 16, State 1, Line 1
Page (1:12472664), object ID 6, index ID 0 has been modified but is not marked modified in the differential backup bitmap.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 99, index ID 0, page (1:12269574). Test (m_slots[0].GetOffset () == PAGEHEADSIZE) failed. Values are 0 and 96.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 99, index ID 0, page (1:12269574). Test (Align(m_slots[-1].GetOffset ()) == Align(m_slots[0].GetOffset () + sizeof(GAMHEADER) + sizeof(DataRecHdr))) failed. Values are 96 and 94.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 99, index ID 0, page (1:12269574). Test (m_slots[0].GetOffset () == PAGEHEADSIZE) failed. Values are 0 and 96.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 99, index ID 0, page (1:12269574). Test (Align(m_slots[-1].GetOffset ()) == Align(m_slots[0].GetOffset () + sizeof(GAMHEADER) + sizeof(DataRecHdr))) failed. Values are 96 and 94.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 299864135, index ID 0: Page (1:10224670) could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 5 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'syscomments' (object ID 6).
CHECKDB found 2 allocation errors and 2 consistency errors in table 'ALLOCATION' (object ID 99).
Server: Msg 8941, Level 16, State 102, Line 1
Table error: Object ID 299864135, index ID 0, page (1:10224670). Test (sorted .offset >= PAGEHEADSIZE) failed. Slot 45, offset 0x1 is invalid.
Server: Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 299864135, index ID 0, page (1:10224670). Test (sorted.offset >= max) failed. Slot 0, offset 0x2d overlaps with the prior row.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 411148510, index ID 0: Page (1:2005832) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 0, page (1:2005832). Test (sorted .offset >= PAGEHEADSIZE) failed. Slot 35, offset 0xc is invalid.
Server: Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 0, page (1:2005832). Test (sorted.offset >= max) failed. Slot 0, offset 0x23 overlaps with the prior row.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 411148510, index ID 0: Page (1:5363504) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 411148510, index ID 0: Page (1:5627224) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 411148510, index ID 0: Page (1:17210894) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 0, page (1:17210894). Test (sorted .offset >= PAGEHEADSIZE) failed. Slot 22, offset 0x1 is invalid.
Server: Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 0, page (1:17210894). Test (sorted.offset >= max) failed. Slot 0, offset 0x16 overlaps with the prior row.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 603865218, index ID 0: Page (1:2729420) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 603865218, index ID 0: Page (1:2729421) could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'Master1_2007' (object ID 299864135).
CHECKDB found 0 allocation errors and 8 consistency errors in table 'Coll_NumCalls_To_Remove_or_Replace' (object ID 411148510).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 603865218, index ID 0: Page (1:2729422) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 603865218, index ID 0: Page (1:2892701) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 603865218, index ID 0: Page (1:2892702) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 796650729, index ID 7, page (1:5363504). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1880277295, index ID 0, page (1:5627224). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
CHECKDB found 0 allocation errors and 5 consistency errors in table 'Acxiom_Opticx_History_to_remove_SN' (object ID 603865218).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 796650729)' (object ID 796650729).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 1880277295)' (object ID 1880277295).
CHECKDB found 2 allocation errors and 26 consistency errors in database 'ArrowProdDB'.
¤ §unshine ¤
August 14, 2008 at 12:08 pm
Thanks.
Was there another line at the bottome, something like "minimum level to repair this error is..."?
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
August 14, 2008 at 12:34 pm
My gut feel is that this database is unrepairable.
There's corruption in one of the system tables (syscomments) and that kind of damage CheckDB is not allowed to repair. In addition, there is damage to what appears to be a GAM (Global Allocation Map) page 1. This is one of the pages that marks which extents within the file are available and which are allocated.
I'm going to see if I can get an expert opinion, but I would guess that your only real option here (since there's no backup) is to script out what you can of the database (some stuff will probably fail to script because of the damage to syscomments) and then bcp out the data that you can, and recreate the database.
Sorry.
(1) as indicated by the line
Table error: Object ID 99, index ID 0, page (1:12269574). Test (Align(m_slots[-1].GetOffset ()) == Align(m_slots[0].GetOffset () + sizeof(GAMHEADER) + sizeof(DataRecHdr))) failed
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
August 14, 2008 at 12:35 pm
No, that was it, still have it up.
¤ §unshine ¤
August 14, 2008 at 12:38 pm
thank you so much. This syscomments is a fairly new error. I've been running checkdb quite often, i can see if it can be restored. The others, well, irrepairable. We are moving to new disk and box, but as you said, i believe as well, the whole db will have to be recreated.
¤ §unshine ¤
August 14, 2008 at 2:10 pm
Yup - this database looks like it will suffer a lot of lost data if you run REPAIR_ALLOW_DATA_LOSS or try to repair the broken GAM pag with undocumented options. From the corruptions, it looks like you've got some pages that have been filled with zeros - classic IO subsystem problems.
My advice is the same as Gail's - move to new hardware and script out as much of the database as you can. Then start running regular CHECKDBs and get a comprehensive backup strategy so you don't get into this situation again. I'd also put on Agent alerts on severity 24 errors so you know as soon as a page corruption like this is picked up by the Engine.
Running REPAIR_REBUILD will never fix problems that CHECKDB has told you that it needs REPAIR_ALLOW_DATA_LOSS as the minimum repair level, and running repair by default isn't a good idea either.
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
August 14, 2008 at 2:27 pm
Thank you!
¤ §unshine ¤
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply