Memory Leak in BCM's SQL Server Desktop Engine?

[Jonathan]

I read that BCM uses the Microsoft SQL Server Desktop Engine (MSDE).

I share my BCM database with two other users.

When I start my system, in Task Manager I see an instance of sqlservr.exe
with "Mem Usage" of just under 30,000K. After a day or two of uptime, that
figure has climbed to over 500,000K.

Is there a known memory leak in BCM/MSDE?

Thank you.

 

[SusanG]

I noticed high mem usage, too. Right now, 65K and it's not shared, and I'm
not transacting data. I'm testing, and this is worrying.

 

[Luther]

This doesn't indicate a memory leak per se.

sqlserver will use available memory to cache tables, indexes, query
plans, etc. It makes sense, if the memory is available and it improves
performance.

That said, it should drop that memory when the OS, has to start paging
memory to disk because there isn't enough to satisfy the demands from
all the running applications.

 

[Jonathan]

This doesn't indicate a memory leak per se. sqlserver will use
available memory to cache tables, indexes, query plans, etc...

To put this in perspective, our BCM database backup (.msbcm) file is 700K.
A (non-BCM) instance of full SQL Server that handles a >50 megabyte database
has memory usage of 45,436K.

But the BCM MSDE instance on my workstation recently passed 500,000K with
minimal activity. After a reboot it has climbed steadily from 29,000K to
113,484K. Recall that the database is less than 1 megabyte. The work-around
of periodic rebooting presents significant operational challenges.

 

[Leonid S. Knyshov]

To put this in perspective, our BCM database backup (.msbcm) file is 700K.
A (non-BCM) instance of full SQL Server that handles a >50 megabyte
database
has memory usage of 45,436K.

But the BCM MSDE instance on my workstation recently passed 500,000K with
minimal activity. After a reboot it has climbed steadily from 29,000K to
113,484K. Recall that the database is less than 1 megabyte. The
work-around
of periodic rebooting presents significant operational challenges.

There are knowledge base articles how to limit SQL memory footprint.

http://support.microsoft.com/default.aspx?scid=kb;en-us;321363

 

[Jonathan]

I reported this to Microsoft... After 46 minutes on the phone, they told me
flat out that there was no leak, and I should Google "sqlservr.exe" and read
about configuring SQL Server.

Anyway, I realized that installing Office maintenance doesn't necessarily
pick up fixed for the SQL Server Desktop Engine, so I downloaded and
installed SQL2000-KB916287-v8.00.2187-x86x64-ENU.exe and the problem may be
fixed. (It's hard to tell as the big BCM user is on the road).

I'll report again when I'm sure.

 

[Jonathan]

Memory usage is now 301,576K bytes, so maintenance didn't help.
A database backup (.msbcm) is now 23,166K bytes.