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 |
|
sasan.kh
Starting Member
23 Posts |
 Posted - 2009-02-04 : 06:03:28
|
| Posted - 02/02/2009 : 02:47:08 Hi allI have a sql server 2000(without any servis packs installed) database with some tables containing near 2-3 million records. recently consistency errors are seen frequently specially on these high record tables... How can I find the source of the problem? and I want to know if index design mistakes can do this...after executing this:DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGSresult was:Server: Msg 8960, Level 16, State 1, Line 1Table error: Page (1:68556), slot 26, column 2 is not a valid complex column.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1435079. The text, ntext, or image node at page (1:97232), slot 85, text ID 55999922176 is not referenced.Server: Msg 2511, Level 16, State 1, Line 1Table error: Object ID 269244014, Index ID 0. Keys out of order on page (1:148), slots 266 and 267.CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.CHECKDB found 0 allocation errors and 1 consistency errors in table 'spJavab_Az' (object ID 1435079).CHECKDB found 0 allocation errors and 1 consistency errors in table 'ICDCodes' (object ID 269244014).CHECKDB found 0 allocation errors and 3 consistency errors in database 'dbSina'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (dbSina ).Best regards |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2009-02-04 : 06:49:13
|
| There have been a few corruption bugs in early versions of SQL Server 2000 (apart from the fact that anything below SP3a is vulnerable to the Slammer virus) that could have caused these exact errors. You should upgrade to SP4 so that you're not exposed to the corruption bugs.Without being on SP4, it's hard to say whether the corruptions are caused by SQL Server bugs or by your I/O subsystem. You might want to checkout your I/O subsystem to see whether its causing errors though - also check the firmware revision level of all drivers and hardware too.ThanksPS To recover from this, best way is to restore from a backup. Worst case you'll need to run REPAIR_ALLOW_DATA_LOSS, which will delete one record from the 'spJavab_Az' table, and rebuild the clustered index (which may or may not fix the out of order keys problem) of the 'ICDCodes' table.Paul S. Randal, Managing Director, SQLskills.com (www.SQLskills.com/blogs/paul)SQL Server MVP, Contributing Editor of TechNet MagazineAuthor of SQL 2005 DBCC CHECKDB/repair codeAuthor & Instructor of Microsoft Certified Master - Database course |
 |
|
|
sasan.kh
Starting Member
23 Posts |
Posted - 2009-02-12 : 08:06:21
|
| THanx so much....I installed SP4 and it seems that the problem is gone.... (till now) |
|
|
|
|
|
|
|
|
Frequent Database consistency errors..