3 replies
by [_rick_>
After you ran ESEUTIL in repair mode, which looks at the physical structure of the database pages (btw may delete some pages), did you run the ISINTEG command to fix any internal Database Table, Row and Column errors.
ISINTEG -pri -fix -verbose -detailed -tests alltests
Run the above at least twice until all errors are gone (some may not surface until the second run through), expect 3-4 hours per GB to complete for the first initial run through.
For more information see the following Technet Article (Q259851):
Ramifications of Running ESEUTIL /P or EDBUTIL /D /R [Q259851]
by marcustech
Rick,
I shall give it a try. At first glance I thought I had already done as you had suggested. I actually had run isinteg but without those parameters and only once. I think that you have the solution.
Thanks very much for your help.
Regards
Mark
by marcustech
This discussion is closed to new replies.
Trending Software posts
Sort by Trending