SQLServerAgent???

  • Thread starter Thread starter William W. Plummer
  • Start date Start date
W

William W. Plummer

I noticed that SQLServerAgent is running on my machine. It might have
started after I did a complete reinstall of Win2KSP4. From the events in
the Event Log, it seems to do something with the network. Can somebody
explain what is going on and if I can shut it down. Thanks.
 
You also must have installed SQL server dev edition, or MSDE or an
application that uses MSDE. Not installed with Windows 2000 by default.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows]
Microsoft Certified Professional
http://www.microsoft.com/protect


:
| I noticed that SQLServerAgent is running on my machine. It might have
| started after I did a complete reinstall of Win2KSP4. From the events in
| the Event Log, it seems to do something with the network. Can somebody
| explain what is going on and if I can shut it down. Thanks.
|
|
 
SQL Server Agent is a task scheduler specifically designed
for SQL Server. As Dave has already said you or someone
must have installed it as it does not come as standard.

As for turning it off, well the problem is that as a task
scheduler it may turn off something you need, or an
application needs.

J
 
William said:
I noticed that SQLServerAgent is running on my machine. It might
have started after I did a complete reinstall of Win2KSP4. From the
events in the Event Log, it seems to do something with the network.
Can somebody explain what is going on and if I can shut it down.
Thanks.

Check Services under Administrative Tools for "SQLAgent$<instance>" where
'instance' will be the name of an SQL Server database. If it is formatted
exactly like I have specified, you should be able to see another service
called "MSSQL$<instance>" where 'instance' will match the name listed next
to SQLAgent$.

If both services are 'started', you are running an instance of SQL Server
(or MSDE) on your computer. If you don't recall specifically downloading
and installing MSDE, then it was installed as part of another application
(i.e. Windows SharePoint Services).

Aside from the resource issues (namely memory), there are significant
security issues related to MS SQL Server (incl. MSDE).

- carl
 
Carl Fenley said:
Check Services under Administrative Tools for "SQLAgent$<instance>" where
'instance' will be the name of an SQL Server database. If it is formatted
exactly like I have specified, you should be able to see another service
called "MSSQL$<instance>" where 'instance' will match the name listed next
to SQLAgent$.

If both services are 'started', you are running an instance of SQL Server
(or MSDE) on your computer. If you don't recall specifically downloading
and installing MSDE, then it was installed as part of another application
(i.e. Windows SharePoint Services).

Aside from the resource issues (namely memory), there are significant
security issues related to MS SQL Server (incl. MSDE).

I found a SQLServerAgent and MSSQLServer but without the "$<instance>".
Also, Data Sources (ODBC) is listed on Control Panel. Is "MSDE" the same as
Microsoft Development Environment? I did reinstall Visual Studio and
believe I selected the full install. Would you advise uninstalling that and
selecting just the parts I really need?
 
William said:
I found a SQLServerAgent and MSSQLServer but without the
"$<instance>". Also, Data Sources (ODBC) is listed on Control Panel.
Is "MSDE" the same as Microsoft Development Environment? I did
reinstall Visual Studio and believe I selected the full install.
Would you advise uninstalling that and selecting just the parts I
really need?

Truth be known, the Visual Studio .NET samples that use SQL Server, such as
the ASP.NET Starter Kits, want the database instance to be named NETSDK by
default. So, if you're not seeing "SQLServerAgent$NETSDK" and
"MSSQL$NETSDK", then you're going to have to re-install the MSDE or SQL
Server Developer Edition again.

During the SQL Server Components Installation, it defaults to the default
SQL server name. You'll want to select the radio button to create a 'named'
instance and type "NETSDK" in the text-box that will be enabled upon
selecting that radio button.

I hope that helps.

- carl
 
Hi, if you don`t need MSDE installed on your machine ,then unnistall it
Start ->control panel -> add /remove programs
But you may be stop services and disable it
Start ->control panel -> Administrative tools->SERvices ->SqlserverAgent
Start ->control panel -> Administrative tools->SERvices ->MsSqlSErver

You need MSDE for work with .NET on conections to database (ADO.NET,ODBC..)

Jose Nadim
 
Jose Nadim said:
Hi, if you don`t need MSDE installed on your machine ,then unnistall it
Start ->control panel -> add /remove programs
But you may be stop services and disable it
Start ->control panel -> Administrative tools->SERvices ->SqlserverAgent
Start ->control panel -> Administrative tools->SERvices ->MsSqlSErver

You need MSDE for work with .NET on conections to database
(ADO.NET,ODBC..)

Thanks for the help. I still don't know what "MSDE" stands for, however.
Is it "MicroSoft Development Environment" and is that the same thing as
Visual Studio?
 
William W. Plummer said:
(ADO.NET,ODBC..)

Thanks for the help. I still don't know what "MSDE" stands for, however.
Is it "MicroSoft Development Environment" and is that the same thing as
Visual Studio?

I want to say Desktop Edition...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top