>>So we have another nasty problem here. How much time would the full search take? And would it hamper the performance of other userrs?
>
>If a full search means to do something like searching for a certain string inside the entire table, without using any index, this is something that can easily bring the server down. So, yes, it would affect everyone.
>
>I am looking at alternatives to answer this type of request. For example, maybe we can force a maximum timeframe of 6 to 12 months, in another type of search, just to look a string as is in the table.
Is that a good idea? A user might do it 10 times to search in five years. And then it would still affect everyone. It's not an easy problem, I'm aware of that.
You might add a checkbox that does that type of search in the resulting cursor of the previous search. Then I could do a normal search on 'sys', resulting in perhaps 100 records. And do the full search of 'sys(1040)' within those 100 records.In order to minimize an overall performance drop, you might enable that checkbox only if the resulting cursor of the first search is less than, let's say, 500 records.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
