Hello,
When running queries, what is the hardware acting like?
Check your Network IO, Ram, CPU. All of these can be seen from Windows Resource Monitor. If all of your hardware is working fine (I.E no visible bottlenecks), it could be a query that is just taking too long. If you can identify a bottle neck, like Disk IO for instance, it could be virtual memory, or some other cache. See if you can identify what is writing (Postgres for instance would be super interesting)...
Examples of bad quires are 'Select *'. There are other examples, but in a nutshell, you don't want to call a bunch of data, put it in memory, and then filter. It is much more efficient to simply filter in the query to put less into memory.
I hope that helps you understand the method to the madness. Please let me know if I can help further. Good luck -
