Has anyone else noticed performance issues when switching from a search criterion using a native date field like trandate vs. the same search using a custom date field? I added a custom field for “Date Paid in Full” to keep a record of transaction status and all of a sudden I have timeouts.

I can't recall a specific instance but it wouldn't surprise me if the native date field is indexed in the DB but your custom field is not.

I wonder if enabling 'global search' on the custom field would improve script search performance (thinking this may index the field). In this case it's moot, as custom date fields (understandably) can not be enabled for global search

Interestingly enough, I waited a few days, and problem solved.