Office 2003 and SQLservr.exe Question...

[Zephyr77]

Hello,

I installed MS Office 2003 Pro and after checking Task Manager, I notice that Sqlservr.exe is running as a new service. Can someone tell me what this service is for?

The reason I ask is twofold. First, it takes up a large amount of memory. After starting my system, Sqlservr is using approx. 15MB but after using the system for a bit, it's memory usage starts to climb, especially after using Outlook 2003 (memory usage went up to 35MB).

Secondly, after checking the Event Viewer, I see a number of warning entries related to MSSQL$MicrosoftBCM. I found a Knowledge Base article (828246) that say's this warning is the result of File & Printer sharing not being installed. Problem is, File & Printer Sharing is installed on my system. Should I reinstall F&P Sharing?

Since installing MS Office 2003, I've started to have system stability issues and am wondering if it could be related to SQLservr.exe? Out of curiosity, I stopped the SQLservr.exe service but then Outlook wouldn't work.

Has anyone else experienced system stability problems after installing Office 2003?

Thanks!
-Zeph

 

[PaulTEG]

SQLServr is Microsoft's Database program SQL Server. It can be a resource hog, depending on what it's doing, but I wouldn't expect it to be doing anything if you haven't configured it to do anything.

What Operating System are you running on?

--Paul

 

[Zephyr77]

Hello Paul,

I'm using WinXP Pro. I didn't configure SQLServr at all. It showed up as a running service after installing Office 2003. I'll have to look aroud a bit more to see if I can turn it off somehow because as you said, it is a huge resource hog. However, it seems Outlook 2003 won't work without it running.

Thanks!

 

[Zephyr77]

OK, I just found out that the reason there is such a tight relationship between the SQLServr and Outlook is because I installed the Business Contact Manager for Outlook 2003. I guess I should have figured that out because of the "BCM" in MSSQL$MicrosoftBCM.

I do want to use the BCM so I'll have to figure out why I'm still receiving the warning in the Event Viewer.