I'm a database management novice, but I was able to figure out that the reason our database maintenance plan is failing. One of the pre-processed tag history tables has 4155 consistency errors.
I don't have any good backups. However, I used a back-up to test REPAIR_FAST, REPAIR_REBUILD, REPAIR_ALLOW_DATA_LOSS.. none of them fixed the issue.
Some of the errors are:
- Keys out of order on page
- The low key value on page .. is not >= the key value in the parent
- The high key value on page .. is not less than the low key value in the parent..
- Page .. was not seen in the scan although its parent .. and previous .. refer to it.
- Page .. is missing a reference from previous page .. . Possible chain linkage problem.
-There are also some duplicate primary keys
There are also hundreds of lines that say "The error has been repaired." but the same number of errors show up every time (4155). That's as far as I could get with what ChatGPT could advise.
Can I drop the pre-processed history table and have the tag historian rebuild it? (or.. drop all of the entries in that table?)
Forgot to add: the database is SQL Server