SQL Server does not start the workaround correctly

By using SEM, right-click the server, click Properties, and then click the Security tab. Under Start the service account, enter the appropriate account and password.

When you install SQL Server2000, you use the default logon user as the account to start the SQL Server service (usually the administrator for the stand-alone computer that you are using), but I changed the username "failed to start service with logon failure" error The following methods I have tried.

1, change the user password back to the original, and then start the service
2, using the control Surface Service Manager, find the MSSQLServer service, change the startup account information, changed to change, and then start the service
3, is also the recommended method, create a new user, specifically to start the SQL Server service, the installation of SQL Server to use the user to start SQL Server, so you can avoid the frequent changes to the administrator password with the 1069 error. If you have installed SQL Server, you can also change the service account information for the MSSQLServer service under the control Surface Service Manager and replace it with a user dedicated to the SQL service.

First, we introduce two common solutions on the network:

1. My Computer--control Panel--management tools--services--right key mssqlserver--properties--landing--Landing identity--Select "Local System Account"

Or:

2. My Computer--control Panel--management tools--services--right key mssqlserver--properties--landing--Landing identity--select "This Account"--Password and Confirm password to enter your modified administrator password.

The difference between the two:

Choose the first way, later modified the administrator password, no more adjustments (but require the system administrator to log on to the operating system)

Select the second way, later modified the administrator password, but also repeat the above operation.

Here's one of the things I've encountered:

This morning my colleague told me that his SQL could not log into his "Enterprise Manager". The reported error is "1069 error, because the login failed to start the service", the Internet to find the above two scenarios, but when I saw the service window and found a possible cause of this problem, the following figure:

We first find the MSSQLServer service, and then look at its properties

Discovery uses a domain account to authenticate when starting a service. Then asked whether the password to change the login domain, get the answer is modified, because the domain has been set, a certain period after the user to change the password, and can not be the same password before (empty password, this I have done experiments ^_^). Then the password is reset here, then restart the service successfully, SQL can also log on successfully.