Skip to main content

Using Max 10 Entrepeneur with 5 users, with database held on a Windows 2008 SBS.

A while back I had a problem with clients whereby queries in Maximizer were running very slowly. I had this investigated, and everything was installed correctly, but it was noticed that the 97% of the physical memory (of 4GB) on my server was in use. It was commented that maybe that was the issue. I duly added another 4GB, and still ended up back at 97% of physical memory in use.

I rebooted the server and the memory usage drops to 35% (of now 8GB), however I can see the memory allocated to instances of sqlservr.exe gradually increase with every query made on Maximizer by a client. If a client exits Maximizer the memory allocation stays at the high level. Basically, it looks like there is an additive effect of every query, that increases until I'm back at 97% of my physical memory being back in use.

Any ideas?
Original Post

Replies sorted oldest to newest

Thanks for the response.

Sorry I wasn't clear. An instance of sqlservr.exe is opened with each client. Each instance doesn't appear to exceed 1GB RAM.

Naturally I have many programs consuming RAM on my server; the overall effect is that other programs (e.g. Exchange) take up around 4GB of RAM. The instances of sqlservr.exe for Maximizer use then grow and grow until I am at 97% of memory use.

I have read this may be normal for sqlservr.exe and the secret is to cap the level of memory used?
A bit more information.

Running tasklist /svc at the command prompt on the server gives me (for sqlservr.exe):

sqlservr.exe 2796 MSSQL$MAXIMIZER
sqlservr.exe 1868 MSSQL$SQLEXPRESS

IT appears the MSSQL$MAXIMIZER memory usage is cumulative for all clients (not separate instances as I mentioned before). This seems capable of exceeding 1GB memory allocation, and has reached 1.4 GB. The MSSQL$SQLEXPRESS sits at around 100,000 KB, and does not really change.
Good Afternoon.

I've had a brief look at the information you've post and I'm afraid I don't think you're going to be able to do anything about it.

If you are running on a full Windows Server I would suggest that you should be running the Pro edition of Maximizer with a proper SQL Server behind it, that way you can control how much memory it can use at once.

Entrepreneur runs on SQL Express that is designed for Workgroups and Single users.
I am surprised that that would be the only answer.

I have used Maximizer for many years in this pseudo workgroup arrangement (albeit pervasive previously). I have many other programmes using sql express without problems. Currently any query run by a Max client results in more memory being allocated to the instance of sqlservr.exe assigned to Maximizer. This interaction is just not right - it peaks at 1.4 GB. I recently had my installation checked out by CABC, and there was no suggestion that this arrangement should not work, and an upgrade would be required.

I will look further into this, but it seems a re-boot is the simplest solution at the moment.

Add Reply

Post
LEGAL INFO
CONTACT US
Copyright 2007-2018 Advoco Solutions Ltd. All Rights Reserved.
×
×
×
×
Link copied to your clipboard.
×