SQLServer and SQLServer Agent services - Startup

[bessebo]

I was wondering what the concensus out there is for startup properties of SQlServer and SQlServer Agent services. We are upgrading from SQL7 to SQL2000 (I know, a little late) and we currently start up the MSSQLServer service under the local System account and we start up the SQLServer Agent under a specific domain account with certain privileges to access network shares. This was done in order to be able to schedule a nightly job that imports data from a network location from an Access database into a SQLServer table.
This is under our SQlServer 7 environment.
With SQL2000 I was thinking of starting both services up with the same network domain account (not the local system account). Or maybe it makes sense to continue starting up the MSSQLServer service with the local system account. I may want to implement SQLMail on this server as well and I think what account SQLServer starts up in affects SQLMail. I would appreciate any information on hos best to start up the two services.

Thanks...

 

[Luvsql]

There's no real reason why the MSSQL Service itself needs to access anything outside of the sql box. THe agent is what runs the jobs and maintenance. When you are configuring sql mail, you must configure it with a domain account as well, which is linked to a mailbox in exchange (ie setup profile with mail icon in control panel).

 

[bessebo]

So it probably makes sense to have the MSSQLServer service start up using the locla system account and the SQLServer agent start up with a domain user account? Do you use SQl Mail? I think it would be really handy in cases of backups failing or any other jobs failing (to be emailed on such an occurrence).

 

[Luvsql]

Definitely have the agent using a domain account. Sql mail is great. It will email any errors with your jobs, let's you know when logs are approaching capacity, etc.

 

[mrdenny]

If you plan on accessing any files on network shares from your apps or Query Analyser you will need the SQL Service setup to run under a domain account.

If you want to use xp_sendmail you'll need the SQL Server setup under the domain account.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[Rousseau10]

what if you in a workgroup and not on a domain??? For example in a classroom environment? use local system account for sql services and something else local I guess for sql agent , what to use for replication???


SUE PER TANKS!

 

[mrdenny]

I'd recommend setting up a domain. That's how most people will be seeing it in the real world.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[bessebo]

I think I will use the same domain account for starting up SQLServer and SQLServer Agent.

 

[timscronin]

Might as well get use to the domain account, we give our sqlexec account domain admin priveleges and firecall it. With web services, Biztalk, and the new version of Exchange which uses sql server for data store it's the better solution

 

[mrdenny]

Giving your SQL Account domain admin rights is very dangerous. In the event that someone is able to break into your SQL Server this would give the attacker domain admin rights to your domain.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[bessebo]

Good point well taken.

Thanks.