Original source: http://blog.csdn.net/dba_huangzj/article/details/38657111, featured catalogue:http://blog.csdn.net/dba_huangzj/article/details/37906349
No person shall, without the consent of the author, be published in the form of "original" or used for commercial purposes, and I am not responsible for any legal liability.
Previous article: http://blog.csdn.net/dba_huangzj/article/details/38656615
Objective:
SQL Server has two types of authentication: Windows Authentication, Windows authentication uses the account on Windows, and authenticates with its security token. One is SQL Server authentication, which is authenticated using an account defined in SQL Server.
Realize:
1. In SSMs, right-click instance Name, select Properties, and then locate the Security page:
Windows authentication only accepts Windows accounts, which is turned on by default and cannot be turned off. SQL Server and Windows Authentication Mode accept Windows and SQL Server accounts.
2. If Windows authentication is selected, you can create a SQL Server relate share, but you cannot use it, and switching authentication requires restarting the service.
Principle:
During the installation process, SQL Server asks for authentication, Windows authentication is the default, and is the recommended setting because it simplifies administration and provides greater security. You cannot disable Windows authentication by using SQL Server authentication only if the user you are accessing exceeds the local network or the environment of a trusted domain.
SQL Server accounts are created inside SQL Server, and both authentication and password authentication are owned by SQL Server.
The recommended scenario is to use Windows authentication and define groups in the Active Directory to add groups to SQL Server only.