Dear all,

We are having hard time with our SQL Server 2000 Standard Edition.

These are a vew of the errors we are receiving:

When trying to start a job in EM/MS, or running some complex SPs:
--------------------
Unable to post notification to SQLServerAgent (reason: MapViewOfFile() returned error 8, 'Not enough storage is available to process this command.')
--------------------

In the SQL Server log when starting we get the warning:
--------------------
Warning: unable to allocate 'min server memory' of 2000 MB.
--------------------

After 1-2 days of work:
--------------------
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"
--------------------

This and other DLL's when performing several actions in EM (like the properties of the server, etc):
--------------------
Cannot load the DLL xplog70.dll 8 (Not enough storage is available to process this command
--------------------

SQL Server Profiler receives the following error after logging in (when displaying the trace grid):
--------------------
Failed to read trace data.
Unspecified error .... (in Profiler 2000)
An unspecified error... (in Profiler 2005)
--------------------

Event Viewer errors:
--------------------
--------------------
17120 :
SQL Server could not spawn process_loginread thread.
-----------
Every 5-15 mins:
--------------------
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
--------------------

RESTARTING SQL SERVER FIXES ALL THE PROBLEMS FOR THE NEXT 1-2 DAYS.


This is our Server:
Windows 2003 Server Standard Edition, 4 processors, 4 GB RAM, more than half of free space on each Disk. It is a dedicated server. No other applications are running on the same server, but SQL.

SQL Server2000 Standard Edition, configured to use fixed 2000 MB RAM, all 4 processors.

We have one main DB that is set, like all the other ones to grow auto matically.

We have cleared all the logs from both the SQL server and SQL server agent.

Questions: Why can't the server allocate the 2000 MB RAM? We have tried with 1000MB and we get no more warning in the log. I have tried with 1999MB. Sometimes I get the error sometimes I don't. With 2000, I always get the error. When SQL Server Agent is not started together with SQL the error does not always appear if the memory is set below 2000 MB (<2000 MB)

I have tried also system managed virtual memory size. The problems reain the same.


We used to believe it's the transaction log of our main DB. and we truncated it. Our complete backup is running every week. The differential is running dayly.
this is what we used ( BACKUP LOG dbname WITH TRUNCATE_ONLY )


The problems stop appearing if the server is restarted, but they appear back in less than one day.


Thank you in advance!

Hi!

The errors indicate that your tempdb is getting filled up due to over-utilization of temp tables and other cases. You should allocate better space for TempDB.
Someone may have configured memory per query of Server option. If you require more specify it.
I am sure there is problem with tempdb, because, as you know restarting is helping you.

Try to allocate better space for tempdb. Also configure the server using EM to get better results.
-Som Dutt