I should add that there are audit records being written based on insert, update and delete triggers.

>in the config i am setting to 7. I am assuming that is global setting. What is happening is everyonce in awhile we are getting false corruption error messages. Also suspect that during some heavy query use on a server with only 10K spindle drives (3), that the reads are maxing out and it seems we get a disconnect from the server and because of that our error reporting is thinking of table corruptions. (Fox DBC's)
>
>Is there extra overhead with the tablevalidate set to 7?
>
>>I would recommend 7 or 15 for SET TABLEVALIDATE to make sure that table corruption not goes undetected.
>>
>>>Having some issues and would be interested in what the recommended settings for
>>>
>>>Set Reprocess To
>>>
>>>and
>>>
>>>Set Tablevalidate To
>>>
>>>and can you give me why you would recommend those settings?
>>>
>>>Thanks in advance