Memory Problem

Hello,
I look after several SQL server DB's, all are SQL 2000 standard edition,
some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
fine and dandy, except for one application that's causing me a headache. Th
e
SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 SP1
,
and sits on a dual processor box with 2GB of RAM.
Through profiler and performance monitor I can see the app logs into SQL,
runs a sql statement, and logs out again - it does this circa 250 times ever
y
30 seconds. The problem I have is SQL keeps on grabbing memory and doesn't
release it, seemingly it's due to this login process (on perfmon I can see
when the logins occur every 30 seconds or so, and using taskmanager I can se
e
inline with this login process the memory sqlservr.exe uses increases). The
memory increases at a rate of around 116mb per hour, and when it hits the
physical limit, SQL crashes. The actual error in the log relates to
CImageHelper:: and dbghelp.dll and gets posted several times before SQL fall
s
over.
Anyone any ideas why this is happening?Sounds like you hit a bug in SQL Server. Are you current on Service Pack? Di
d you search KB for the
related error messages? If you still didn't find anything, you should open a
case with MS.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
> Hello,
> I look after several SQL server DB's, all are SQL 2000 standard edition,
> some are SP3, some are SP4, some are Win 2000, some are Win 2003. All is
> fine and dandy, except for one application that's causing me a headache.
The
> SQL DB behind the app is SQL 2000 standard edition SP4, it's on Win 2003 S
P1,
> and sits on a dual processor box with 2GB of RAM.
> Through profiler and performance monitor I can see the app logs into SQL,
> runs a sql statement, and logs out again - it does this circa 250 times ev
ery
> 30 seconds. The problem I have is SQL keeps on grabbing memory and doesn'
t
> release it, seemingly it's due to this login process (on perfmon I can see
> when the logins occur every 30 seconds or so, and using taskmanager I can
see
> inline with this login process the memory sqlservr.exe uses increases). T
he
> memory increases at a rate of around 116mb per hour, and when it hits the
> physical limit, SQL crashes. The actual error in the log relates to
> CImageHelper:: and dbghelp.dll and gets posted several times before SQL fa
lls
> over.
> Anyone any ideas why this is happening?|||Thanks for the reply Tibor, We're on SP4 (which is current), Can't find any
KB articles that cover the issue, can't find anything on web at all really (
a
part from a couple with slight relavance)
"Tibor Karaszi" wrote:

> Sounds like you hit a bug in SQL Server. Are you current on Service Pack?
Did you search KB for the
> related error messages? If you still didn't find anything, you should open
a case with MS.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:A8248C82-7633-4092-B334-B910B47FE063@.microsoft.com...
>
>|||I did a quick Google search and I guess we found similar cases. Not exactly
your case. My guess is
that your code hit a memory leak in that code section of SQL Server, and tha
t you would need
assistance from MS to either work around it or have them prepare a hotfix fo
r you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BenUK" <BenUK@.discussions.microsoft.com> wrote in message
news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply Tibor, We're on SP4 (which is current), Can't find an
y
> KB articles that cover the issue, can't find anything on web at all really
(a
> part from a couple with slight relavance)
> "Tibor Karaszi" wrote:
>|||Thanks for your help Tibor :-)
"Tibor Karaszi" wrote:

> I did a quick Google search and I guess we found similar cases. Not exactl
y your case. My guess is
> that your code hit a memory leak in that code section of SQL Server, and t
hat you would need
> assistance from MS to either work around it or have them prepare a hotfix
for you.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BenUK" <BenUK@.discussions.microsoft.com> wrote in message
> news:8391C053-4B6B-4AEF-8193-8FAC4B056B87@.microsoft.com...
>
>|||If you do get a fix would you mind posting it so we can see what
happened....thanks.
--
burt_king@.yahoo.com
"BenUK" wrote:
[vbcol=seagreen]
> Thanks for your help Tibor :-)
> "Tibor Karaszi" wrote:
>|||no problem, will do
"burt_king" wrote:
[vbcol=seagreen]
> If you do get a fix would you mind posting it so we can see what
> happened....thanks.
> --
> burt_king@.yahoo.com
>
> "BenUK" wrote:
>|||You can increase machine to 3GB, and let SQL Server use full 2gb and leave
1GB for OS.