Multiple Instances of SQL Server Service Manager

- I am running SQL Server 2000 (Standard Edition, SP3) on a Windows Server
2003 (Standard, v5.2) server operating in terminal services mode. The SQL
Server Service Manager is in the startup folder for all users, so multiple
instances are running when more than one user is logged in.
- I am having some problems with this server, so I'm trying to stop anything
that doesn't need to run.
- Can I delete the SQL Server Service Manager from the all users startup
folder? (I would start Service Manager when the Administrator logs in.)
- Thanks.Hi
SQL Server Service Manager is not required for SQL Server operation. You can
remove it from the startup folder.
You can still manage SQL Server though Enterprise Manager and Control Panel
> Services.
Any reason you have a server that SQL Server needs to share with Terminal
Server users? It is not an optimal configuration.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave" wrote:
> - I am running SQL Server 2000 (Standard Edition, SP3) on a Windows Server
> 2003 (Standard, v5.2) server operating in terminal services mode. The SQL
> Server Service Manager is in the startup folder for all users, so multiple
> instances are running when more than one user is logged in.
> - I am having some problems with this server, so I'm trying to stop anything
> that doesn't need to run.
> - Can I delete the SQL Server Service Manager from the all users startup
> folder? (I would start Service Manager when the Administrator logs in.)
> - Thanks.|||Mike,
- Thanks for the info.
- Re your question, I am running Act2005 (which uses SQL2000) for a company
that offices virtually. We setup this server in a hosted datacenter, and
loaded all of our apps (Act, MSOffice, a cpl others) and access everything
using terminal services on the server and remote desktop connection on the
client PCs.
- This configuration generally works, although there are some bugs which I
attribute to the poor job done by my IT provider, and the fact that Act2005
is not designed for terminal services. My only big problem is that Act
occasionally starts using a lot of memory (over 1GB of VM in some cases) and
the whole server slows down.
- Thanks again for your help, and please let me know if you have any
suggestions for my configuration.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> SQL Server Service Manager is not required for SQL Server operation. You can
> remove it from the startup folder.
> You can still manage SQL Server though Enterprise Manager and Control Panel
> > Services.
> Any reason you have a server that SQL Server needs to share with Terminal
> Server users? It is not an optimal configuration.
> Regards
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Dave" wrote:
> > - I am running SQL Server 2000 (Standard Edition, SP3) on a Windows Server
> > 2003 (Standard, v5.2) server operating in terminal services mode. The SQL
> > Server Service Manager is in the startup folder for all users, so multiple
> > instances are running when more than one user is logged in.
> > - I am having some problems with this server, so I'm trying to stop anything
> > that doesn't need to run.
> > - Can I delete the SQL Server Service Manager from the all users startup
> > folder? (I would start Service Manager when the Administrator logs in.)
> > - Thanks.