peterdru401 (3/25/2013)
You should keep track on SQL Server storage and performance to avoid this type of problemIf the capacity management of sql server is up to the mark then sql server always perform well and you will never face this type of problem
you can try some third party software for capacity management of SQL server which will give you accurate information.
1. this has nothing to do with storage and 2. the issue can occur whether SQL Server has enough memory or not. It's mostly related to a misalignment between Windows memory management approach (i.e. how Windows is coded) and SQL Server behavior and cannot always be cured by adding more memory or lowering 'max server memory'.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato