SQL Server does not succeed in modifying the SA password after the extraction process

Today to work to open the computer, found that all the project started after the error, the reason is that the database SA validation error, unable to database links and so on things, simply say---SQL Server cramps!!! : (

It was a good day yesterday. And I haven't changed anything. Why is there a problem? I again on the internet to collect a lot of information is not done, asked the company's technical leadership has not been done. Later on their own research, I would like to share my experience with you, if you encounter this problem can be quickly resolved!

General common practice:

1. Connect the database with Windows authentication first. ( nonsense, no connection how to change the password for internal settings!) )

2. Locate the root directory of the Object Explorer and click the Right button property.

3. Find security and set it to SQL Server and Windows Authentication compatibility mode ( so you can enter the database in a later SQL Server input password!) ), close the Options box.

4. Locate the security in the directory, locate the subdirectory's login name, and find the SA ( which is called the admin login mode ), right-click to find the property.

5, after you can change the password, and confirm the password. Isn't it simple? Hehe, do you have a few questions? For example, 1 places, is not 15, but your password is 2 bits (such as:SB),

is not the difference too many, there is no? this is because the system will generate some interference codes inside, when the need to extract the password is that it will reflect the generation of a new password. The new generated password is the 2-bit password you set (SB) all over the world the software does this, not explained . There is a very important thing, the network of the Great God did not mention the place, here to everyone said, the figure of 2, if you click on the "Enforce password Policy", then the following mandatory password expiration will be automatically checked, then congratulations, your password must contain at least one lowercase letters, a capital letter, A number, otherwise invalid, the system will not prompt you Oh!!! It's disgusting!

6. After the new password is generated, it must be restarted before it can be generated successfully. Remember, it's not shutting down, okay, reboot! After locating the root directory, right click on restart. Otherwise the direct shutdown is no use dripping!

7, after opening the connection, appears. It's another 15-bit password. This is OK, above we said, this password and your 2-digit password is the same relationship. Click Connect. Is the heart very excited? Hey, the result you are not logged on drip!! , you do not feel particularly bitter, or re-install the software or reinstall the system. Oh, I am very responsible to tell you that you have done so the chances of success of recovery is almost less than 20%.

8. What can I do to restore it? In fact, it is not difficult to say the concrete way first.

After you open the database with Windows authentication, create a new query, enter the following code, and manually set the new, password. After that, it's OK!

9, although successful, but why our previous operation is not successful? The reason is that the property setting is useless, the default password data is still in memory, requires manual code operation to modify its data password, clear the memory password. And you cannot close the database but restart the option to take effect. If you do not manually, the system will always call the internal retention of the password, think you how to change are not successful drip ! Hope can help everyone.

10. Finally, take a look at the glorious picture we signed in!

SQL Server does not succeed in modifying the SA password after the extraction process