Any issues with running SQL Server 2000 Standard Edt. on a 4GB server?

Hi,
we have a project where my company and another company is using the same sql
server, the problem is that the sql server crashes approximately every 3-4
days, with something that looks like memory related issues where we get the
following errors in the eventlog just before it crashes:
17120 : SQL Server could not spawn process_loginread thread.
The other company is using some COM objects (asphttp from
www.serverobjects.com) from some stored procedures to call a website(these
are called several thousand times a day) and I think that is the problem
since i can crash my own sql server and several other development sql
servers with calling this COM object through storedprocedues several
thousand times with what looks like a memory leak as sql server uses more
and more memory the more times these stored procedures are called... the
other company of course say that they have been using this product for years
without problems.
Now the other company insists that there is problems with having 4GB memory
in the server and running the standard edition of sql server 2000. We are
not using /3GB switch in boot.ini and yes we know that standard edition of
sql server can only use 2GB max.
Anyone experienced any problems like this before on a similar setup, that
too much ram will kill sql server? because i sure haven't.
Server specs:
Dual 3Ghz Xeon, 4GB ram, Mirrored Raid, HP/compaq branded server running
windows server 2003 standard edition.
SQL Server 2000 standard edition with the latest service packHi
The COM object is leaking the memory and not SQL. SQL can't control it as it
is running in process. Tell them to run the test on their machine a few
million times in a loop and watch their server fall over.
I have seen this many times and it does not matter how much RAM you have.
Regards
Mike
"T. Schmidt" wrote:
> Hi,
> we have a project where my company and another company is using the same sql
> server, the problem is that the sql server crashes approximately every 3-4
> days, with something that looks like memory related issues where we get the
> following errors in the eventlog just before it crashes:
> 17120 : SQL Server could not spawn process_loginread thread.
> The other company is using some COM objects (asphttp from
> www.serverobjects.com) from some stored procedures to call a website(these
> are called several thousand times a day) and I think that is the problem
> since i can crash my own sql server and several other development sql
> servers with calling this COM object through storedprocedues several
> thousand times with what looks like a memory leak as sql server uses more
> and more memory the more times these stored procedures are called... the
> other company of course say that they have been using this product for years
> without problems.
> Now the other company insists that there is problems with having 4GB memory
> in the server and running the standard edition of sql server 2000. We are
> not using /3GB switch in boot.ini and yes we know that standard edition of
> sql server can only use 2GB max.
> Anyone experienced any problems like this before on a similar setup, that
> too much ram will kill sql server? because i sure haven't.
> Server specs:
> Dual 3Ghz Xeon, 4GB ram, Mirrored Raid, HP/compaq branded server running
> windows server 2003 standard edition.
> SQL Server 2000 standard edition with the latest service pack
>
>
>|||I tried using another com object(w3socket www.dimac.net) that does the same
thing and called the stored procedure 100.000 times, and sql server didn't
use anymore memory during the test. I did the same thing with the com object
i suspect leaking and could see that sql servers private bytes was rising
slowly but steadily. That has to be a good indication of a leak wouldn't you
say?
I used process explorer from system internals to monitor sql server.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:04F273D3-1FEE-4B6A-A7F8-9AC074D79ECE@.microsoft.com...
> Hi
> The COM object is leaking the memory and not SQL. SQL can't control it as
it
> is running in process. Tell them to run the test on their machine a few
> million times in a loop and watch their server fall over.
> I have seen this many times and it does not matter how much RAM you have.
> Regards
> Mike
> "T. Schmidt" wrote:
> > Hi,
> >
> > we have a project where my company and another company is using the same
sql
> > server, the problem is that the sql server crashes approximately every
3-4
> > days, with something that looks like memory related issues where we get
the
> > following errors in the eventlog just before it crashes:
> >
> > 17120 : SQL Server could not spawn process_loginread thread.
> >
> > The other company is using some COM objects (asphttp from
> > www.serverobjects.com) from some stored procedures to call a
website(these
> > are called several thousand times a day) and I think that is the problem
> > since i can crash my own sql server and several other development sql
> > servers with calling this COM object through storedprocedues several
> > thousand times with what looks like a memory leak as sql server uses
more
> > and more memory the more times these stored procedures are called... the
> > other company of course say that they have been using this product for
years
> > without problems.
> >
> > Now the other company insists that there is problems with having 4GB
memory
> > in the server and running the standard edition of sql server 2000. We
are
> > not using /3GB switch in boot.ini and yes we know that standard edition
of
> > sql server can only use 2GB max.
> >
> > Anyone experienced any problems like this before on a similar setup,
that
> > too much ram will kill sql server? because i sure haven't.
> >
> > Server specs:
> >
> > Dual 3Ghz Xeon, 4GB ram, Mirrored Raid, HP/compaq branded server running
> > windows server 2003 standard edition.
> >
> > SQL Server 2000 standard edition with the latest service pack
> >
> >
> >
> >
> >