Database keeps getting corrputed

Hi,

I have a problem with an 2K5 (v9.0.3042) database. For about 3 tables, several nonclustered indexes are getting corrupt every week. I droppped and recreated these indexes, did a DBCC CHECKDB and everything was ok, but the problem re-appears after several days. Tables and indexes which are giving problems are always the same. The only thing I see is that autoshrink is enabled (low diskspace)

Any help would be appreciated!

Wilfred

asked Mar 17 '10 at 07:22 AM in Default

Apeman
311 ● 11 ● 12 ● 15

(comments are locked)

3 answers:

Hi,

In SQL-2000,for a self updated query which is updating huge number of records we may find that non-clustured indexes is corrupted.In this case B-tree structure for the non-clustured indexes also corrupts.You may notice database corruption sometimes.Applying latest service packs on OS and SQL is one option to recover.second restore NCI back from the backup sets.May i know which DBCC command you ran?

answered Mar 17 '10 at 08:01 AM

venkatreddy
562 ● 26 ● 28 ● 32

it's MSSQL 2005

Mar 17 '10 at 08:40 AM Apeman

hey,u can do the same for 2K5.y did u voted in negative?

Mar 17 '10 at 09:19 AM venkatreddy

(comments are locked)

Grants suggestion of getting Paul in is a good suggestion.. Also search through his blog as he pretty my mind dumps all his knowledge on DBCC to there.

http://www.sqlskills.com/BLOGS/PAUL/category/Conferences.aspx

http://www.sqlskills.com/BLOGS/PAUL/category/Repair.aspx

What DBCC CHECKDB command are you running?

In some cases it it possible that the file system is at fault. I would do the necessary check on the disks themselves too.

answered Mar 17 '10 at 07:44 AM

sp_lock
8.1k ● 20 ● 26 ● 29

Yes, absolutely. It really could be hardware. I should have thought of that. +1

Mar 17 '10 at 08:20 AM Grant Fritchey ♦♦

DBCC CheckDB() with NO_INFOMSGS

Mar 17 '10 at 08:35 AM Apeman

Get your O/S Admins to do a full hardware diagnostic. It could be drives, RAM or something else. A single bit switched in transit...

Mar 17 '10 at 04:22 PM Blackhawk-17

I would lean towards hardware as well. I can't imagine that SQL Server corrupts a table in particular because of data in it or some command being run

Mar 18 '10 at 03:53 PM Steve Jones - Editor ♦♦

(comments are locked)

That's a very abnormal situation. Are you sure you're on the latest service packs on your OS and on SQL Server? Are you getting errors prior to, or in conjunction with the corruption?

Honestly, something like this, I'd call in the Marines, or Paul Randal.

answered Mar 17 '10 at 07:30 AM