many problems, fixed?

Hi All-
SQL7.0 SP0 NT4. I was brought in to help fix this database, backups are
there, but corruption has been in the maintenance plan log for over a year.
I made backup of db and restored as different name on different disk array.
I ran DBCC CHECKDB on database, it reported 17,000+ consistency errors. I
next rebuilt indexes and ran CHECKDB again. Dropped errors to 202. Ran
CHECKDB with repair_rebuild option. This corrected some errors, now I am
down to 94. Since it was a copy I gave it a shot and ran CHECKDB with
repair_allow_data_loss option. After this ran, CHECKDB reports 0 errors. I
have compared row count on corrupt tables before and after the data_loss
option ran and my row count is the same before and after.
What else do I need to look at to see what data was loss with the
repair_data_loss option?
After ths is correct I will be working with the owner and app vendor to get
the sql and os at least patched to current levels if not upgraded.
Thanks!I suppose you could check the size of the database and the number of indexes
in it. It doesn't sound like you have much of a choice but to go with the
repaired database anyway.
Good luck...
Ben
"Ryan Sanders" <rsanders> wrote in message
news:108nd8uapvjvbb2@.corp.supernews.com...
> Hi All-
>
> SQL7.0 SP0 NT4. I was brought in to help fix this database, backups are
> there, but corruption has been in the maintenance plan log for over a
year.
> I made backup of db and restored as different name on different disk
array.
> I ran DBCC CHECKDB on database, it reported 17,000+ consistency errors. I
> next rebuilt indexes and ran CHECKDB again. Dropped errors to 202. Ran
> CHECKDB with repair_rebuild option. This corrected some errors, now I am
> down to 94. Since it was a copy I gave it a shot and ran CHECKDB with
> repair_allow_data_loss option. After this ran, CHECKDB reports 0 errors.
I
> have compared row count on corrupt tables before and after the data_loss
> option ran and my row count is the same before and after.
>
> What else do I need to look at to see what data was loss with the
> repair_data_loss option?
>
> After ths is correct I will be working with the owner and app vendor to
get
> the sql and os at least patched to current levels if not upgraded.
>
> Thanks!
>|||Can anyone provide any guidance?
Thanks!
Ryan
"Ryan Sanders" <rsanders> wrote in message news:<108nd8uapvjvbb2@.corp.supernews.com>...
> Hi All-
>
> SQL7.0 SP0 NT4. I was brought in to help fix this database, backups are
> there, but corruption has been in the maintenance plan log for over a year.
> I made backup of db and restored as different name on different disk array.
> I ran DBCC CHECKDB on database, it reported 17,000+ consistency errors. I
> next rebuilt indexes and ran CHECKDB again. Dropped errors to 202. Ran
> CHECKDB with repair_rebuild option. This corrected some errors, now I am
> down to 94. Since it was a copy I gave it a shot and ran CHECKDB with
> repair_allow_data_loss option. After this ran, CHECKDB reports 0 errors. I
> have compared row count on corrupt tables before and after the data_loss
> option ran and my row count is the same before and after.
>
> What else do I need to look at to see what data was loss with the
> repair_data_loss option?
>
> After ths is correct I will be working with the owner and app vendor to get
> the sql and os at least patched to current levels if not upgraded.
>
> Thanks!