Hi all, I've been working with a customer who was experiencing sporadic results when trying to run large scale searches against the journal using search.asp
The box is Virtual, 4 core 8gb (now 12gb), Ev10, Windows Server 2008 r2 Standard
I've resolved the problem to be the stored procs on SQL timing out because of the scale of the searches, the inefficiency of search.asp to perform the objective they seek (it's a legal search - they need DA)
I solved the problem in the short term by removing FederatedResults and advising them to do the search in smaller chunks - which is working
My question: is there a way of calculating what resources would be necessary to perform a search, so I can help them scale properly for their current and future needs? I need to advise them to up the resources on there VM - like add another core and bump the RAM up to 16gb, but without being able to specify why I think that, it's a bit like hit and hope
Any ideas?