SQL Service Account
-
HI,
I have installed a sql server 2005 EE and started the SQL Server as well as Agent Service with the domain accounts.
But Now i want to change the Services to start with a different domain accounts but its not giving me to change the Service account.
The Service is not restarting after changing the Domain accounts.
Please let me know what needs to be done.
-
How did you change the service account? You should change the service account using SQL Server Configuration Manager because doing so will ensure that the new account is given the necessary permissions in SQL Server. If you changed the account using the Windows Services Applet this won't happen.
-
goto windows services and select SQL Server instance, choose properties and navigate to Log on tab...
-
what error message are you getting in event viewer?
-
Are you certain that SQL2005 EE will allow you the rights to do that function? We had some developers install SQL 2005 Express and some tasks and functions were not allowed. Verify what your version can do on the microsoft site.
-
Check the rights on the machine for the new account.
Might need to give it more rights. Quick check is to add it to the local admin group on the box SQL is running on.
-
You should be weary of ever changing any service account through any means other than SQL Configuration Manager, this includes the Windows services menu. SQL Configuration Manager does a lot more than change the service account for a windows service. When you make a change, the configuration manager actually adds the login to a local windows group(SQLServer2005MSSQLUser). This group has rights to make SQL run including binary/registry items, file_paths, etc.. You can directly add your user to this group but best practice suggests that you use the configuration manager.
I would try the configuration manager again. You could probably change the account back to the working domain account or local system and then change it to the new domain account. This should clear up the issues.
-
Check the rights on the machine for the new account.
Might need to give it more rights. Quick check is to add it to the local admin group on the box SQL is running on.
The services do not require admin privelages. Giving the service account eleveated rights is not a best practice.
Use a domain user account
Specifies a domain user account that uses Windows Authentication to set up and connect to SQL Server. Microsoft recommends using a domain user account with minimal rights for the SQL Server service, as the SQL Server service does not require administrator account privileges.
The SQL Server Agent account must have administrator privileges if you create CmdExec and ActiveScript jobs that belong to someone other than a SQL Server administrator, or if you use the AutoRestart feature. If the above features are requirements in your environment, consider using separate service accounts for the SQL Server and SQL Server Agent services.
-
Adam Haines (3/21/2008)
Check the rights on the machine for the new account.
Might need to give it more rights. Quick check is to add it to the local admin group on the box SQL is running on.
The services do not require admin privelages. Giving the service account eleveated rights is not a best practice.
Agreed - However when troubleshooting it can help rule out permissions issues. Wouldn't advise leaving it like that.
-
touche friend. I just didnt want the OP to make the change and leave it like that.
-
Right! that would be a bad idea for sure! And it's easy to say ok it works now, and move on to the next problem/issue
-
Is the problem already solved?
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply