If you've got SQL Agent jobs running at a certain time, it is to be expected that there will be a spike in memory usage then, so nothing's necessarily wrong.

If there is a problem, you may be able to spread the jobs out to even the load, or possibly run them overnight.

Looking for a simple solution - If you identify a problem time & there's only 1 job running, then that is the problem.

SQL Server doesn't keep stats about run durations etc by default - you need to generate them yourself. A good way is using Profiler. If you create a trace & run it for the period of interest, this can tell you which queries are slow. There's a lot of info about this on the web. Bear in mind that running a trace will add to the load on the server, so only run it when needed. A good source of information is "Mastering SQL Server Profiler" by Brad McGehee - see chapter 4 "How to identify slow-running queries".

You can download this book for free.

Try this:

download.red-gate.com/ebooks/SQL/Mastering_Profiler_eBook.pdf