multiple instances of sqlservr.exe process

I have a Windows Server 2003 with SQL server 2000
installed. Whenever I view the Task Manager/Processes I
see three entires for the sqlservr.exe process. I am
thinking this is not normal and must be causing certain
performance issues I am facing. Whenever the server has
been up for a few hours the server starts getting slower.
If I reboot the server everything stays fine for a few
hours but then it starts slowing down. I have 2GB of RAM
on the server, about 20 Gigs free space on the C: drive
and about 120 Gigs free space on the data drive. All the
database files are stored on the data drive. Any help or
pointers in the right direction would be greatly
appreciated.
LakshmanHow many services whose name starts "MSSQL" do you see when you look in
Services ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Lakshman" <hlokku@.hotmail.com> wrote in message
news:2a3801c3fc98$efbaef60$a301280a@.phx.gbl...
> I have a Windows Server 2003 with SQL server 2000
> installed. Whenever I view the Task Manager/Processes I
> see three entires for the sqlservr.exe process. I am
> thinking this is not normal and must be causing certain
> performance issues I am facing. Whenever the server has
> been up for a few hours the server starts getting slower.
> If I reboot the server everything stays fine for a few
> hours but then it starts slowing down. I have 2GB of RAM
> on the server, about 20 Gigs free space on the C: drive
> and about 120 Gigs free space on the data drive. All the
> database files are stored on the data drive. Any help or
> pointers in the right direction would be greatly
> appreciated.
> Lakshman|||Hello Lakshman,
Please monitor the following.
Memory\Available Bytes (Threshold<4MB)
Memory\Pages/sec (Threshold>20)
PageFile\ % Usage (Threshold>70%)
Physical Disk\Avg. Disk Queue Length ( Threshold: > 1.5 x # of spindles )
Physical Disk\% Disk Time (Threshold: >90% )
SQLServer:Memory Manager/Total Server Memory (per instance)
Also make sure your patch level is up to date on the SQL server and the OS.
Did you install any extended stored procs?
"Lakshman" <hlokku@.hotmail.com> wrote in message
news:2a3801c3fc98$efbaef60$a301280a@.phx.gbl...
> I have a Windows Server 2003 with SQL server 2000
> installed. Whenever I view the Task Manager/Processes I
> see three entires for the sqlservr.exe process. I am
> thinking this is not normal and must be causing certain
> performance issues I am facing. Whenever the server has
> been up for a few hours the server starts getting slower.
> If I reboot the server everything stays fine for a few
> hours but then it starts slowing down. I have 2GB of RAM
> on the server, about 20 Gigs free space on the C: drive
> and about 120 Gigs free space on the data drive. All the
> database files are stored on the data drive. Any help or
> pointers in the right direction would be greatly
> appreciated.
> Lakshman|||I do not see any processes with "MSSQL" but there are 2
processes that say "sqlmangr.exe"
Lakshman.
>--Original Message--
>How many services whose name starts "MSSQL" do you see
when you look in
>Services ?
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"Lakshman" <hlokku@.hotmail.com> wrote in message
>news:2a3801c3fc98$efbaef60$a301280a@.phx.gbl...
>> I have a Windows Server 2003 with SQL server 2000
>> installed. Whenever I view the Task Manager/Processes I
>> see three entires for the sqlservr.exe process. I am
>> thinking this is not normal and must be causing certain
>> performance issues I am facing. Whenever the server has
>> been up for a few hours the server starts getting
slower.
>> If I reboot the server everything stays fine for a few
>> hours but then it starts slowing down. I have 2GB of RAM
>> on the server, about 20 Gigs free space on the C: drive
>> and about 120 Gigs free space on the data drive. All the
>> database files are stored on the data drive. Any help or
>> pointers in the right direction would be greatly
>> appreciated.
>> Lakshman
>
>.
>|||He was referring to Services:
Start -> Settings -> Control Panel -> Administrative Tools -> Services
<anonymous@.discussions.microsoft.com> wrote in message
news:294a01c3fca6$83b713d0$a501280a@.phx.gbl...
> I do not see any processes with "MSSQL" but there are 2
> processes that say "sqlmangr.exe"
> Lakshman.
> >--Original Message--
> >How many services whose name starts "MSSQL" do you see
> when you look in
> >Services ?
> >
> >--
> >HTH
> >
> >Jasper Smith (SQL Server MVP)
> >
> >I support PASS - the definitive, global
> >community for SQL Server professionals -
> >http://www.sqlpass.org
> >
> >
> >"Lakshman" <hlokku@.hotmail.com> wrote in message
> >news:2a3801c3fc98$efbaef60$a301280a@.phx.gbl...
> >> I have a Windows Server 2003 with SQL server 2000
> >> installed. Whenever I view the Task Manager/Processes I
> >> see three entires for the sqlservr.exe process. I am
> >> thinking this is not normal and must be causing certain
> >> performance issues I am facing. Whenever the server has
> >> been up for a few hours the server starts getting
> slower.
> >> If I reboot the server everything stays fine for a few
> >> hours but then it starts slowing down. I have 2GB of RAM
> >> on the server, about 20 Gigs free space on the C: drive
> >> and about 120 Gigs free space on the data drive. All the
> >> database files are stored on the data drive. Any help or
> >> pointers in the right direction would be greatly
> >> appreciated.
> >> Lakshman
> >
> >
> >.
> >|||If you have multiple sqlservr.exe process showing up then you have multiple
instances of SQL Server running on this server. There are a multitude of
applications that install a copy of MSDE 2000 and use it as a data store.
If you did not purposely install the instances of SQL Server then more than
like other applications did. BackUp Exec uses MSDE, so if you have it
installed on this server that would explain one of the instances.
As Adam said, check:
Start -> Settings -> Control Panel -> Administrative Tools -> Services
You should see multiple services that start with MSSQL.
Rand
This posting is provided "as is" with no warranties and confers no rights.

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:
[vbcol=seagreen]
> 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
> 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:
sql

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.

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 anythi
ng
> 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:
[vbcol=seagreen]
> Hi
> SQL Server Service Manager is not required for SQL Server operation. You c
an
> remove it from the startup folder.
> You can still manage SQL Server though Enterprise Manager and Control Pane
l
> 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:
>

Multiple instances of SQL

According to the Task Manager, on my SBS 2003 Server, I'm running multiple instances of SQL. How do I determine which instance(s) are required to maintain server stability, and which are not. My Server resource use continues to be a perennial problem. Please advise.

Hi,

perhaps this article at Database Journal help Monitoring SQL Servers Availabilty.

|||

You most likely have the following instances, for the stated purposes.

MSSQL$SHAREPOINT -necessary if you are using Sharepoint Services
MSSQL$SBSMONITORING - necessary for internal usage of SBS

MSSQLSERVER - Default SQL Server that may be used by your applications.

Other instances may be installed and required for various third party products.

I would not stop the first two, and only stop the third IF there are no applications requiring SQL Server.

It really sounds like you need to explore more memory or CPU power for your SBS server.

Multipile Instance in MSDE

I have installed 2 MSDE 2000 engines in to the PC. one is no instance name, another one's instance name is 'TEST'.

I could use a GUI MSSQL manager to connect both with local machine.

But when I tried to connect both with other machine, I found that I only could connect either one which is start in service earlier.

My case is normal?

Are they conflict by the same network port? If yes, could I change the portnumber of the MSDE??

Thanks for your support!!Hi Walama,

I haven't used MSDE a whole lot, but it does sound like changing the port number might be the trick.

The SVRNETCN.EXE program can do that for you. SVRNETCN.EXE configures the remote protocol for your MSDE instances - but maybe you already know that because it sounds like you got at least one instance hooked up.

You can select which instance to configure, what protocol and the "Properties..." button for TCP/IP has a place to set a port number.

The program is located in your "C:\Program Files\Microsoft SQL Server\80\Tools\Bin" folder.

I posted some screen-shots of how to connect to MSDE from Enterprise Manager recently - although I haven't done the write up yet.

http://kb.xmlx.ca/article.aspx?id=10065

Hope this helps...|||Hi Scott,

Thx for you suggestion. I am changing the port number now, but I want to know that if I use the 3rd party tool to manage the database. So do you know how do I enter the portnumber for those tools??