What are gotchas for starting Sql & the agent with a Local system account
versus a system Domain account.

Hi

IMO the main reason to use a domain account is permissions (lack of, or too
high) and the ability to assign them to the account.

John
[quoted text, click to view]

AHartman (Hoosbruin@Kconline.com) writes:
[quoted text, click to view]

One gotcha that people run from time to time, is that they want to access
network shares from SQL Server, for instance for BULK INSERT. This does not
work with Local System. Another gotcha is that SQL debugging from another
machine usually does not work if you are running under local system.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at

In article <Xns95A8D9056DF1CYazorman@127.0.0.1>, esquel@sommarskog.se
says...
[quoted text, click to view]

Actually, of you understand NET USE, then you don't have to have the SQL
Server in the domain. If you provide the credentials it works just fine.

In most cases, where there is some form of web interface, even for a
intranet, I always setup the servers without providing Domain User
account access to it. The one exception being an application that uses
Windows Authentication Accounts, instead of a programatic method, to
access data.

--
--
spamfree999@rrohio.com