Warning: OPEN OBJECTS parameter may be too low. | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Warning: OPEN OBJECTS parameter may be too low.

Any idea it will be highly appreciated!
More info It is a Win 2000 server with SQL Server 2000 SP3a, 2GB RAM. Dynamic allocated memory. I am getting also messages at the crush time 2004-06-21 09:59:11.90 logon Login failed for user ‘nsain’.
2004-06-21 10:00:30.70 spid10 Warning: OPEN OBJECTS parameter may be too low.
2004-06-21 10:00:30.70 spid10 Run sp_configure to increase the parameter value.
2004-06-21 10:00:30.84 spid10 Warning: OPEN OBJECTS parameter may be too low.
2004-06-21 10:00:30.84 spid10 Run sp_configure to increase the parameter value.
2004-06-21 10:01:45.14 spid14 Warning: OPEN OBJECTS parameter may be too low.
2004-06-21 10:01:45.14 spid14 Run sp_configure to increase the parameter value.
2004-06-21 10:03:10.48 spid54 Warning: OPEN OBJECTS parameter may be too low.
2004-06-21 10:03:10.48 spid54 Run sp_configure to increase the parameter value.
2004-06-21 10:03:12.53 spid3 Error: 701, Severity: 17, State: 127
2004-06-21 10:03:12.53 spid3 There is insufficient system memory to run this query.. also at the boot I am getting a
2004-06-21 09:38:01.48 server initdata: Warning: Could not set working set size to 834720 KB.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_config_0pm6.asp for information and use SP_CONFIGURE to increase the Open Objects parameter. BTW what is the current value set for OPEN OBJECTS?
How about memory settings on SQL? Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
it is zero, the default. I read the article it didn’t help me. It was zero it get cheanged after I try to fix the memory allocation Now I had open objects0214748364710001000 I run the sp_configure to change it back to 0 and look like open objects0214748364701000
[ Warning: Could not set working set size to 834720 KB. The reason for this is that you are trying to set a working size for a non-fixed memory configurarion. Either turn the "set working set size" advanced sp_configure option to 0 (the default), or set "min server memory" and "max server memory" to the same value. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>