SQL Server memory leak? 1

[ElTech]

My production server (MSSQL 2000 Server with Service pack 4) is set to use Dinamically configured memory at 4MB to 1503MB max. After a few days, the process sqlservr.exe is using 1,609,560 K and growing. The host operating system is Windows 2000 with Service pack 4. The applications using the server are Heat (call logging 7.00 build 120) and Goldmine. The server does have Oracle 8i client installed to import data using a DTS package from a Oracle datbase server.

Below is the DBCC MEMORYSTATUS, but I have no idea what it means even after reading several articles about it.

c:\>osql -E
1> DBCC MEMORYSTATUS
2> go
Buffer Distribution Buffers
------------------------------ -----------
Stolen 2557
Free 73
Procedures 125503
Inram 0
Dirty 3480
Kept 0
I/O 0
Latched 73
Other 60698

(9 rows affected)
Buffer Counts Buffers
------------------------------ -----------
Commited 192384
Target 192384
Hashed 64251
InternalReservation 254
ExternalReservation 0
Min Free 64
Visible 192384

(7 rows affected)
Procedure Cache Value
------------------------------ -----------
TotalProcs 67612
TotalPages 125503
InUsePages 70892

(3 rows affected)
Dynamic Memory Manager Buffers
------------------------------ -----------
Stolen 128060
OS Reserved 928
OS Committed 906
OS In Use 898
General 3473
QueryPlan 125213
Optimizer 0
Utilities 15
Connection 177

(9 rows affected)

Global Memory Objects Buffers
------------------------------ -----------
Resource 1386
Locks 53
XDES 8
SQLCache 1718
Replication 2
LockBytes 2
ServerGlobal 21

(7 rows affected)

Query Memory Objects Value
------------------------------ -----------
Grants 0
Waiting 0
Available (Buffers) 89205
Maximum (Buffers) 89205

(4 rows affected)
Optimization Queue Value
------------------------------ -----------
Optimizing 0
Waiting 0
Available 8
Maximum 8

(4 rows affected)
DBCC execution completed. If DBCC printed error messages, contact your system
administrator.


1> DBCC SQLPERF(UMSSTATS)
2> go
Statistic Value
-------------------------------- --------------
Scheduler ID 0.0
num users 27.0
num runnable 0.0
num workers 9.0
idle workers 6.0
work queued 0.0
cntxt switches 2585522.0
cntxt switches(idle) 2087132.0
Scheduler ID 1.0
num users 26.0
num runnable 0.0
num workers 9.0
idle workers 5.0
work queued 0.0
cntxt switches 2711313.0
cntxt switches(idle) 2593629.0
Scheduler Switches 0.0
Total Work 5327205.0

 

[MDXer]

From experience I know that HEAT is a major resource hog, especially if BPAM is running.

Shoot Me! Shoot Me NOW!!!
- Daffy Duck