Hello,
A group that audits process compliance has requested a monthly notification containing all of the Tasks of a specific type and I've been tasked with providing it. I looked around the documentation and found a script for calculating the months since an item was created. I created a custom calculated field and bound it to the months since creation script. I then built a filter which looks for all items with 0 or 1 in the field and seem to get the right data. About 10 minutes after I finish this option, the response time for TS increases by 2 orders of magnitude (went from 20-40 msec to 5-10 minutes). When I was defining the custom field, I chose not to have the value cached (thinking it would make the database engine run off and calculate it for everything in the database). Would adding a non-cached calculated custom field to a database of about 7000 items cause that type of performance hit? Should it clear up? I have several users that must be able to use TS in a timely fashion.
If the method I chose to implement is causing the problem, is there an alternative that shouldn't have as much overhead? Ideally I'd like to be able to provide this information with minimal impact to normal data processing.
