Heres a more detailed task manager view... As you can see SQL isn't consuming all the memory like sometime it can. Seems a bold statement to make to only recommend 3.5 GB... Just the first three processes would consume more than that. It might not be "active" memory, but the memory pushed out because of ballooning or potential swapping could cause major performance problems.
I'd like to know if anyone at any point has ever been in a place where they felt comfortable implementing the suggestions outlined by the report.
