sqlservr.exe (MSSMLBIZ) holding onto memory

[BobTrudo]

When Outlook 2007 w/Business Contact Manager (BCM) starts, it opens an
instance of sqlservr.exe (MSSMLBIZ) which begins to latch onto a lot of
memory - sometimes upwards of 350MB in a 1GB RAM system (XP Home). With
close to 450 entries in BCM, this startup takes considerable time.
Ultimately, it does complete and BCM shows the Accounts and Business
Contacts. What is bothersome is the fact that the BCM instance of
sqlservr.exe holds onto a great deal of memory - even when Outlook 2007 is
closed. This forces other applications to use the swap file with a
considerable slowdown in performance. By manually stopping the MSSMLBIZ
service (after verifying there is no longer any disk activity in Task
Manager), performance is restored. Is there some startup option for MSSMLBIZ
(or the BCM startup service [bcmsqlstartupsvc.exe] that can force MSSMLBIZ
service to terminate, or at least release excess memory after Outlook is
closed down?

 

[Brad Covell]

I believe that SQL Server is still running even after you close Outlook. It
is possible to set the maximum amount of memory that the MSSMLBIZ SQL
Instance uses by following the instructions below. We have been successful
setting the max to 256MB without any problems, in fact scaling back the
memory probably will increase the performance of not only XP but of BCM
itself.

Third, set the SQL memory for the client machines. By default each client
machine will have SQL Server 2005 Express installed on it, this installs
with Outlook BCM. By default the maximum amount of memory that SQL Server
2005 Express can use is 2147483647MB, that's huge and unnecessary for BCM.
Download and install the SQL Management tools
(http://www.microsoft.com/downloads/...AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en)
on each client machine. Connect to the local SQL Express server and right
click on the server within the management studio and choose Properties.
Within the pane that comes up, click the Memory link and set the Max Amount
of memory to 256MB. That's plenty for BCM. Click OK and it's done

http://officepoint.blogspot.com/2008/09/improve-outlook-bcm-business-contact.html

- Brad

 

[BobTrudo]

Thanks, Brad. Reducing the max memory did help. But, it would still be nice
to have it close the instance of sqlservr.exe (MSSMLBIZ) because even 256MB
is a considerable of the available 1GB RAM. Thanks again...

I believe that SQL Server is still running even after you close Outlook. It
is possible to set the maximum amount of memory that the MSSMLBIZ SQL
Instance uses by following the instructions below. We have been successful
setting the max to 256MB without any problems, in fact scaling back the
memory probably will increase the performance of not only XP but of BCM
itself.

Third, set the SQL memory for the client machines. By default each client
machine will have SQL Server 2005 Express installed on it, this installs
with Outlook BCM. By default the maximum amount of memory that SQL Server
2005 Express can use is 2147483647MB, that's huge and unnecessary for BCM.
Download and install the SQL Management tools
(http://www.microsoft.com/downloads/...AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en)
on each client machine. Connect to the local SQL Express server and right
click on the server within the management studio and choose Properties.
Within the pane that comes up, click the Memory link and set the Max Amount
of memory to 256MB. That's plenty for BCM. Click OK and it's done

http://officepoint.blogspot.com/2008/09/improve-outlook-bcm-business-contact.html

- Brad

When Outlook 2007 w/Business Contact Manager (BCM) starts, it opens an
instance of sqlservr.exe (MSSMLBIZ) which begins to latch onto a lot of
memory - sometimes upwards of 350MB in a 1GB RAM system (XP Home). With
close to 450 entries in BCM, this startup takes considerable time.
Ultimately, it does complete and BCM shows the Accounts and Business
Contacts. What is bothersome is the fact that the BCM instance of
sqlservr.exe holds onto a great deal of memory - even when Outlook 2007 is
closed. This forces other applications to use the swap file with a
considerable slowdown in performance. By manually stopping the MSSMLBIZ
service (after verifying there is no longer any disk activity in Task
Manager), performance is restored. Is there some startup option for
MSSMLBIZ
(or the BCM startup service [bcmsqlstartupsvc.exe] that can force
MSSMLBIZ
service to terminate, or at least release excess memory after Outlook is
closed down?