I'm using Sql server n 2005 developer in an as needed basis with Visual
studio 2005. A day ago I installed Sp1,
and found that now the visual studio gives me package loading errors. I've
posted about that in the visual studio forum. Beyond that, perhaps based on
what I had done manually, or perhaps not, I've looked in the services for
the Windows 2003 Server I use as a testbed and found that I have most of my
sql server services set on manual start: sql server, sql server agent, sql
server analyses services, sql server browser, full text search, integration
services, reporting services, vss writer.

What should I have on automatic, and what can I keep on manual to minimize
system load unless I'm actually using the service???

Thanks

In order that the SQL Server data engine be available, you should have the
SQL Server (MSSQL) service running, and set to 'Automatic'.

The remainder are only needed when you are using functionality they may
provide.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


"charlestek" <charlestek@yahoo.com> wrote in message
news:esgx9tr1GHA.4748@TK2MSFTNGP04.phx.gbl...
> I'm using Sql server n 2005 developer in an as needed basis with Visual
> studio 2005. A day ago I installed Sp1,
> and found that now the visual studio gives me package loading errors.
> I've posted about that in the visual studio forum. Beyond that, perhaps
> based on what I had done manually, or perhaps not, I've looked in the
> services for the Windows 2003 Server I use as a testbed and found that I
> have most of my sql server services set on manual start: sql server, sql
> server agent, sql server analyses services, sql server browser, full text
> search, integration services, reporting services, vss writer.
>
> What should I have on automatic, and what can I keep on manual to minimize
> system load unless I'm actually using the service???
>
> Thanks
>

If you are just using SQL Server developer when needed and
you want to reduce system load when it's not in use, just
set all of the services to manual. There is no need to keep
any of them running all the time. When you need to use any
of the services, just start the SQL Server service and then
whatever other services you need for what you are doing.

-Sue

On Tue, 12 Sep 2006 18:33:45 -0400, "charlestek"
<charlestek@yahoo.com> wrote:

>I'm using Sql server n 2005 developer in an as needed basis with Visual
>studio 2005. A day ago I installed Sp1,
>and found that now the visual studio gives me package loading errors. I've
>posted about that in the visual studio forum. Beyond that, perhaps based on
>what I had done manually, or perhaps not, I've looked in the services for
>the Windows 2003 Server I use as a testbed and found that I have most of my
>sql server services set on manual start: sql server, sql server agent, sql
>server analyses services, sql server browser, full text search, integration
>services, reporting services, vss writer.
>
>What should I have on automatic, and what can I keep on manual to minimize
>system load unless I'm actually using the service???
>
>Thanks
>