May 25, 2010 at 11:55 am
Hi Folks
I just installed SQL Server 2008 Developer Edition on a Windows 2008 Server - 64-bit
I have a question about these Local SQL Server Groups that were created below:
SQLServerDTSUser$NSAB-SS73-SQL-N
SQLServerFDHostUser$nsab-SS73-sql-n$MSSQLSERVER
SQLServerMSASUser$NSAB-SS73-SQL-N$MSSQLSERVER
SQLServerMSSQLServerADHelperUser$NSAB-SS73-SQL-N
SQLServerMSSQLUser$nsab-SS73-sql-n$MSSQLSERVER
SQLServerReportServerUser$NSAB-SS73-SQL-N$MSRS10.MSSQLSERVER
SQLServerSQLAgentUser$NSAB-SS73-SQL-N$MSSQLSERVER
just what are these groups used for ?
do i need to add my log on service into these groups that start up my sql services ?
In addition this one below was also created and if you look at the name it says "2005"
So I am confused as to why it says 2005 and not 2008.
Anyone else see this
SQLServer2005SQLBrowserUser$NSAB-SS73-SQL-N
You can check under Server Manager>Local Users and Groups>Groups
Thanks
Jim
May 26, 2010 at 3:55 am
This was removed by the editor as SPAM
May 26, 2010 at 2:09 pm
hi stewartc-708166
not sure what you mean
these are local groups
i want to know if i need the account that logs on to all the sql services added to these groups ?
my other servers seem to have it
Jim
May 26, 2010 at 11:23 pm
This was removed by the editor as SPAM
February 6, 2016 at 4:54 am
Can anyone confirm that this is a comprehensive list of the permissions?
http://www.databasesql.info/article/124980796/
Integration Services
Default instance or a named instance: SQLServerDTSUser $ ComputerName
The service capacity Login (SeServiceLogonRight,)
Write access to the application event log.
Bypass traverse checking (SeChangeNotifyPrivilege)
Authentication Impersonate a client after (SeImpersonatePrivilege)
SQL Server Agent 3
Default instance: SQLServerSQLAgentUser $ ComputerName $ MSSQLSERVER
Named instance: SQLServerSQLAgentUser $ ComputerName $ InstanceName
The service capacity Login (SeServiceLogonRight,)
As a batch job the Login (SeBatchLogonRight)
Replace a process level token (SeAssignPrimaryTokenPrivilege)
Bypass traverse checking (SeChangeNotifyPrivilege)
Adjust memory quotas (SeIncreaseQuotaPrivilege)
SQL Server
Default instance: SQLServerMSSQLUser $ ComputerName $ MSSQLSERVER
Named instance: SQLServerMSSQLUser $ ComputerName $ InstanceName
Service capacity login (SeServiceLogonRight)
As a batch job the Login (SeBatchLogonRight)
Replace a process level token (SeAssignPrimaryTokenPrivilege)
Bypass traverse checking (SeChangeNotifyPrivilege)
Adjust memory quotas (SeIncreaseQuotaPrivilege)
Permission to start SQL Server Active Directory Helper
Start SQL Writer's permission
Permission to read the event log service
Permission to read the Remote Procedure Call service
Jamie
February 28, 2016 at 10:38 pm
If we add/change the SQL server service a/c from configuration manager then all the required/necessary permissions are automatically granted.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply