SQL Server Service id | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

SQL Server Service id

Env: SQL2K and SQL2k5 on Win2k3 Is it good idea to have ONE domain user id for SQL Server service for ALL production servers? Or it is suggested to have a domain user id for each server separately? CanadaDBA
It depends… there is nothing wrong in starting all the service using same account. I have seen such organisations which have Job Administrator kind of role. His responsibility is to monitor/administer/maintain jobs. in such case he may be responsible for SQL Server Agent service. so in such scenario you may need to have different accounts for these services. But generally, if there is not such administrative/political problem , it is better to have same account for all the services http://msdn2.microsoft.com/en-us/library/ms143691.aspx Madhu
Now a days sox reasons, it is better to have serperate login for each server….
MohammedU.
Moderator
SQL-Server-Performance.com
See my blog:http://sqlserver-qa.net/blogs/tools…r-domain-account-for-sql-server-services.aspx in this case.q Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
I found the following on this site: In any case having 1 (single) domain account for 150+ and odd SQL Server instances is a ‘bad practice’ in terms of security aspect. Using a mass attack if the attacker gains the password for that domain account the risk is very high in losing all the SQL Server instance in 1 shot which could lead to a great businss loss. So at this juncture it is better to differentiate the usage of those 150+ SQL instances to the business and set an individual account for every SQL instance that has primary business functionality. If the other SQL instances that are used internally for any Intranet based application then you might consider to use 1 domain account for those few instances for managebility. http://www.sql-server-performance.com/faq/sqlviewfaq.aspx?faqid=188 CanadaDBA
Well that was posted by me, missed that on FAQ and as suggested you have to consider the list of SQL servers with 1 domain account for service critical ones you might need each of them. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
]]>