Hey friends - I could have sworn I came across a SuiteAnswers article a long while ago that talked about how NetSuite generates the actual SQL query on the backend for saved searches. IIRC, it essentially said that the order of criteria shouldn't matter since it evaluates all your criteria and generates the most efficient version of that when doing the actual SQL query. I'm fighting with support about saved search performance and thus looking to reference this article. Can anyone point me in the right direction?

I've always heard the opposite. My goal is to always cut the fat at the top of the criteria, esp for large datasets like transactions.

> evaluates all your criteria and generates the most efficient version of that when doing the actual SQL query For what it's worth, Stanley the AI bot says it's this one when I asked recently. But obviously I have no idea where it's getting that information. I've never been able to find it in any formal document either.

If this is true, from my experience the Oracle optimiser is absolutely terrible at ORs. If your query is super slow, it may be because of this

Yeah, it's not really a performance issue per se. I have a search that works fine, and then when I add some additional criteria (that reduces the number of records to be returned) it completely borks the search and times out. NetSuite is claiming that adding text fields to the criteria is what is doing this, but if their process works the way I've been led to believe, this is a defect, not standard behavior.