Two instances of sqlservr.exe in processes list

My home computer (XP Pro SP2) is not connected to a network or any other computer. Since I have owned the computer (Oct 2006), there has always been on instance of sqlservr.exe running in the list of processes within task manager. Now there are two, which confuses me. The only recent changes that I have made to my system is I uninstalled and reinstalled Office Professional 2003 and uninstalled and reinstalled Business Contact Manager for Outlook.

Could my uninstall/reinstall have caused another instance of sqlservr.exe to run? Is it possible to determine which instance is necessary, if either truly is? Should I leave well enough alone as I am not experiencing any problems?

Thanks all!

Drew

 

This link should help you find out more info on sqlservr.exe, and how to remove it.

http://www.processlibrary.com/directory/files/sqlservr/

Scroill down the page to read more about it.

Bazza

 

I ran into that site earlier (Google search) and was confused by it.

First, in the description section, it says that it is essential and should not be terminated. Next, in the recommendation section, it says that it is not a critical component. All that I see regarding removal (if that is what I should do) is a link to WinTasks, which they want me to buy.

Thanks for your help, Bazza. Can you clarify what this site is trying to say?

Drew

 

As you state, you are not connected to a network, so you should be able to remove it. USD$50 is a bit steep. There must be other ways of removing it.

@major geeks@ Any sequel server users out there? Can anyone help?
It is beyond my knowledge. Bazza

 

What do you have that requires sql server?

Is it possible that you have two programs that need a database? That could cause two to run.

As for getting rid of sql server, I had it on my vaio when I got it and ended up having to reinstall vista on it to get rid of it.

 

Thanks padams, for taking up the battle. :cool
Bazza

===

 

I don't even know what requires sqlservr.exe. It is running on my work computer (one instance at 60,000Kb memory), which is connected to a network. But on my home computer, the one with the two instances (one at 12,000 and one at 9,000), I'm not connected to anything but the internet, wirelessly.

As I mentioned, the second one showed up around the time I reinstalled MS Office 2003 and Business Contact Manager for Outlook. I always had one running but now there are two. Does BCM initiate another sqlservr.exe process?

I don't have anything abnormal on my computer, so I don't even know what to tell you could be needing the other process. My set up is really very boring.

 

So you really don't even need sql server, right?

No prob Bazza!

 

Not that I am aware, but as I said, I'm not sure exactly what it does.

The two instances together are not taking up that much in the way of resources. Perhaps I should just leave well enough alone. It's just that the change all of a sudden bothers me.

 

In add/remove programs, does it tell you what version of sql server you have?

Do you think it could be for Business Contact Manager?

 

It could be BCM, I'm not sure. If anyone here has Office 2003 and has also installed BCM for Outlook, they could check their processes and report on this.

In add/remove I have only this: Miscrosoft SQL Server Desktop Engine (MICROSOFTSMLBIZ). No other sql servers on the list.

Drew

 

That's weird. If it were me I'd uninstall it.

 

If I uninstall the sql server, what will I no longer be able to do that I was previously able to do (whether or not I was actually using it)?

Would you also remove BCM for Outlook or do you think that is not an issue?

 

The Business Contact Manager does use sqlserver. If you kill or remove the SQL Server, you will not be able to use BCM. As far as the other instance of sqlserver.exe, one instance is for you, the other is the system's instance. I think that both are needed for SQL Server to run properly.

 

Thank you sir! I makes sense then that the second instance showed up about the time I installed BCM.

Thanks to all who worked with me on this!

Drew