November 6, 2007 at 4:03 pm
In an attempt to fix table problems on a SQL Server 2000 production database I ran the following:
select * into sysindexes_repair from sysindexes with the result - I/O error (bad page ID) detected during read at offset 0x000000d2d12000 in file 'C:\ADP\RR\DATABASES\Concours_CRM_DATA.MDF'.
Connection broken
select * into DEALS_STATUS_HISTORY_repair from DEALS_STATUS_HISTORY with the result- I/O error (bad page ID) detected during read at offset 0x0000005fb44000 in file 'C:\ADP\RR\DATABASES\Concours_CRM_DATA.MDF'.
Connection Broken
@@version yields - Build 2195: Service Pack 4
From what I have read I have either hardware problems or arcane database problems. Any suggestions on which way I should proceed?
November 6, 2007 at 5:50 pm
You could probably start by reviewing your backup strategy, because you may need to restore data here.
First, what does the disk subsystem look like? If you have RAID-N drives where N is greater than 0, then the database file(s) are likely to be the problem, not the disks. (this is a general rule - there are exceptions). In all cases, you need to get a Hardware specialist to evaluate the health of the underlying disk drives - and do it fast.
Depending on how critical the data is, you could choose to RESTORE your last backup, and all of your log backups up to the point when the file went bad, and go from there. This, of course, assumes a backup strategy is available beyond backups to a different partition on the same physical drive(s). Sometimes, you are resource constrained.
So - how critical *is* this data?
November 6, 2007 at 8:18 pm
Thanks for the advice, I'm going to heed your words. The data is pretty critical, it belongs to a very large car dealership group. The backups are actually failing on the production database because of file errors, if I remember right. I noticed this after posting my question. I'll post more info tomorrow when I get a chance, and assuming I get this fixed I'll post that too.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply