>We are consistantly receiving a series of error messages
>with the following:
>Attempt to fetch logical page 1019250 in database XXX which
>belongs to object 'Y' not to object 'Z'
>We have dropped and rebuilt the objects, cycled the data cache,
>and reindexed, all to no -avail. If anyone has an idea what could cause
>these errors, please let us know.
It's a serious error and one that should be corrected at once. Run a
checkdb on the affected database to find out the object id of the
problem table. Then run a checktable with no index. If the
checktable comes back without errors then the problem is on an index
and you can drop and recreate your indexes. If the checktable with no
index reports the error, you have a 605 on the data chain and it's
more problematic. Restore from a known good backup.
If your backup is too old or not valid, you can try copying out the
data. If you have a unique non-clustered index, you can *try* forcing
that index in a select statement to see if you can retrieve the rows.
You may get lucky. Also, if you have a clustered index on the table,
you can try selecting all the rows and order by the clustering key(s)