A script to sync logins between availability group replicas, keeping the SID so users do not orphan on failover. What to copy and what to check after.
How to Enforce Password Policy of Windows to SQL Server? – Interview Question of the Week #142
SQL Server logins follow Windows password rules by default. If a login has it turned off, here is a simple script to Enforce Password Policy again.
SQL SERVER – Login Failed – Error: 18456, Severity: 14, State: 38 – Reason: Failed to Open the Explicitly Specified Database
Error 18456 State 38: failed to open the explicitly specified database. The login worked and the database did not. The four usual causes.
SQL SERVER – FIX: Msg 15170, Level 16, This login is the Owner of 1 Job(s). You Must Delete or Reassign these Jobs Before the Login can be Dropped
Msg 15170: this login is the owner of 1 job(s) and cannot be dropped. Here is how to find those jobs and reassign them first.
SQL SERVER – Msg 15137, Level 16 – Error Related to sp_xp_cmdshell_proxy_account
A client using a proxy account to run xp_cmdshell hit Msg 15137 with sp_xp_cmdshell_proxy_account. Here is what causes the error and how I fixed it.
SQL SERVER – xp_logininfo – Msg 15404: Could not obtain information about Windows NT group/user, error code 0x2147
xp_logininfo failed with Msg 15404 for some users, yet worked for the same user in another domain. Here is what to check to find the difference.
SQL SERVER – Login Failed. The Login is From an Untrusted Domain and Cannot be Used with Windows Authentication
Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. Here is how the ERRORLOG led me to the cause.