> From: Brenda Price > 1. <<snip> only necessary to rebuild the index(es) when you > have a known corruption issue. <<snip> Management decision > from a long time ago and it is our comfort level to continue. > I agree in principal with not rebuilding, but do not have > 100% faith in any technology providing 100% reliability. > 99.9% is sometimes not good enough. When clients are relying > on us to provide their financials via web reports on a timely > and accurate basis that .1% could lose us a big client and > lots of money if it was wrong.
Rather than rebuilding them, I would encourage you to just verify they are ok. Here's a way with no impact on your production system: Restore the file and its indexes TO your dev/test system FROM your standard backup (I assume you back up when the db is quiet!) Be sure to use SET.INDEX to correct the path. Then compare what's in the index with what should be in the index. I have a routine that does that, but I think a better way would be to ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
