The difference between sql sever authentication and Windows authentication
Both Windows authentication and SQL authentication are a type of database authentication, and authentication is used to identify the identity of the operator of the data.
Both of them need to be granted permissions in the SQL Manager before they can operate within the scope of the permissions.
Windows authentication is more secure than mixed mode. When using this connection mode, sql does not judge the sa password, but only performs authentication based on the user's windows permissions. We call it "trusted connection", but it will be affected by remote connections. Cannot log in due to NTML authentication.
When a remote user accesses it because it has not passed the windows authentication, the sql server authentication is performed (users using sa can also log in to sql) to establish a "untrusted connection" so that the remote user can also log in.
How to log in with sql sever authentication
Use Windows authentication to log in to sql sever
After logging in, we can see the "Object Explorer" on the left and find the "Login name sa" in the "Security" below. Right-click "sa" to open the "Login Properties" page, and click "General", Perform password and confirm password operations, then uncheck "Enforce password policy" and click "Confirm".
Change login properties-two buttons under status:
Open our configuration manager, select the protocol under the network configuration, and change the status to "enabled"
As shown in the figure: open the SQL Sever service to see this name
Right-click the name and click "Properties", change the built-in account, and click "OK". It succeeded! (This method was seen by a big boss, no one else has written about this method.)
select the protocol under the network configuration, and change the status to "enabled"
