Well to keep it simple, it has been observed that SQL Does not deallocate memory with memory pressure as well as in previous versions of SQL Server and Windows (Non R2’s).
So it is a Good Idea to use Min and Max SQL Server Memory Settings with SQL R2 and Win R2
I saw these errors in one of our Network Monitoring Server and this being a highly transactional and critical 2005 database server there was no room for “ OOPS!! “.
Use flag –g512 as the SQL Server Start up Parameter, then restart SQL Server. The error will no longer appear in the SQL server Error Log. The CPU and Memory be with in acceptable limits after this change.
I also disabled the Query parallelism because of the Queries Slowness and the Deadlock occurring in the error Log. I did this and it worked for this server, and in this environment.
sp_configure ‘show advanced options’,’1′
reconfigure with override
sp_configure ‘max degree of parallelism’,’1′
reconfigure with override
Which min version do you still work on?
Total Voters: 74
Loading ...