[/quote]

Connections to the database take resources and do consume memory. That added to the waits that Grant asked about would help to understand memory pressure.

Did you check with your users to find out where the app is slow?[/quote]

We only found active 50 connections....which is not much. In additions to SQL using all the memory, we are also getting some error as below.

'A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) ", and also error 40 displayed in certain web application.'

However, this is only happening occasionally and everything else looks fine from the database end.

SueTons.