
	Home > Enterprise Desktop Tips > > Run SQL Server as a domain account for network access

Enterprise Desktop Tips:

EMAIL THIS

TIPS & NEWSLETTERS TOPICS

Run SQL Server as a domain account for network access

Serdar Yegulalp, Contributor
04.11.2006
Rating: --- (out of 5)

Digg This!

StumbleUpon

Del.icio.us

Like many services, SQL Server and the SQL Server Agent can run in a variety of account contexts. By default, both SQL Server and the Agent are installed in the Local System Account context. However, Microsoft notes in one of its own discussions that the Local System Account is provided for backward compatibility only, and it has privileges that SQL Server Agent (and perhaps SQL Server itself) does not require.

For that reason, many security-conscious administrators elect to run SQL Server and SQL Server Agent in a reduced-privilege context. Unfortunately, they sometimes choose a context that's too restricted, especially if SQL Server or the Agent needs to make network connections to or from another host (such as a database server). An account that's too restrictive will prevent SQL Server from accessing the network at all and may make it almost unusable. This applies to both TCP/IP and Named Pipes protocols, since Named Pipes uses the protected IPC$ network share resources.

If you recently changed credentials for SQL Server and have trouble getting the service to authenticate network connections, start checking account permis...

Digg This!

StumbleUpon

Del.icio.us

RELATED RESOURCES

	2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
	Search Bitpipe.com for the latest white papers and business webcasts
	Whatis.com, the online computer dictionary

sions. Microsoft recommends creating a domain user account that has no administrative rights but can access the network. If you switched SQL Server to a domain user account, but didn't grant that account type access to the network as an inherited privilege, make sure you explicitly grant that permission and see what happens. (The only other caveat with using a domain account is that the account has to be authenticated on a domain controller.)

About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter. Check it out for the latest advice and musings on the world of Windows network administrators -- and please share your thoughts as well!

More information from SearchSQLServer.com

Tip: Setting up SQL Server clusters on a SAN

Undocumented DBCC: Report on settings with DBCC RESOURCE>

Stored procedure: Examining SQL Agent job run history

Rate this Tip
To rate tips, you must be a member of SearchEnterpriseDesktop.com. Register now to start rating these tips. Log in if you are already a member.
Submit a Tip

DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

Enterprise Desktop Security - Virus Protection, Malware Protection, Intrusion Detection

SEARCH

TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.


TechTarget Corporate Web Site \| Media Kits \| Site Map All Rights Reserved, Copyright 2008 - 2009, TechTarget \| Read our Privacy Policy