Sounds more like your SQL server.
Can you tell me more what should check in my SQL Server ?
Sorry, but when things run slow I go to my DBA and say, "Hey, it's slow, make it run faster" and then it starts running better.
I know LOTS of memory and indexes seem to be common words I hear. Otherwise I don't know much and have not seen much. Not sure I have ever seen a doc or post of tips for tuning SQL server. I believe our SQL install is fairly vanilla other than it's a cluster.
I don't completely agree with you because I think that this issue is not related to Database performance but with IIS especially
Error Message is about "Time Out" and not about insufficient memory / resources
I make the same search in Test environment (ISO to Prod) and I get query results : No error
It seems a problem of number of connection to web servers that causes the issue ( this is difference of Test and Live environment)
A case ticket was opened and waiting for a response
In IIS you can see the queue of items being processed, the processor, and memory. I have only 1 server and things run great. On my test server I have exactly the same setup which should be overkill for a single user. Yet I get time out errors when saving processes and windows from time to time in my test environment. The biggest difference is that the SQL server has far less memory and I am sharing it with many other apps. That's why I assumed it was SQL. Will be interesting to see what support says and what it takes to fix the issue.
Issue was about increasing sql timeout in TPS as proposed bu Support
tested and worked fine now i can get filter's results even if i search on not indexed field such as 'description'
Thank you simpson@kumc;edu for advises