To check a single table, use DBCC CHECKTABLE. If there is only a
non-clustered index problem, rebuild the index using DBCC DBREINDEX. Check
for integrity of the whole database with DBCC CHECKDB. If ou have major
problems, it could be that your HDD has errors.
To prevent errors, use RAID 1, RAID 5 or RAID 10 arrays of disks for your
Always have backup strategy.
Dejan Sarka, SQL Server MVP
FAQ from Neil & others at: [url]http://www.sqlserverfaq.com[/url]
Please reply only to the newsgroups.
PASS - the definitive, global community
for SQL Server professionals - [url]http://www.sqlpass.org[/url]
"Rene" <nospam.nl> wrote in message
news:vg7lujcbogfg06corp.supernews.com...> Suddenly in one database we have a lot of errors, it seams some things are
> corrupted. I tried to start maintanance / database repair, but this fails
> When selecting in Query yzer a range of records from a table I get the
> following message:
> Location: p:\sql\ntdbms\storeng\drs\include\record.inl:1447
> Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
> SPID: 68
> Process ID: 1208
> When I select the record that causes this error, the following error is
> reported in Query yzer:
> Could not find the index entry for RID '163748993200' in index page
> (3:373352), index ID 0, database 'sal'.
> In the log I see a lot of these messages:
> Stack Signature for the dump is 0x&D179C48
> Could not open FCD for invalid file ID 21761 in database'sal'
> I/O error (bad page ID) detected during read at offset 0x00000b64d2000
> How can this be fixed?
> How can I rebuild the index for one table / check integrity of one table?
> What kind of actions may caused this corruption (if it is corruption) ?
> How can it be prevented?
> I hope someone can help.