Login failed for user with state 58? Newer SQL Server versions give better details in the ERRORLOG. Here is how to FIX Error 18456 when you see this state.
SQL SERVER – Unable to drop login – Msg 15170, Level 16, State 1
Cleaning up my demo server, I could not drop login danny because of Msg 15170: the login owns a job. Here is how to find what a login owns and remove it.
SQL SERVER – Login failed for user . Reason: Token-based server access validation failed
Login failed for user. Reason: Token-based server access validation failed. Here is how the state of error 18456 in the ERRORLOG shows the cause and fix.
Add a User Across Databases: A Tested Script With Cleanup
To add a user across databases you need one login and, in every chosen database, a user and a role. This post gives a tested script that does it, checks it and removes it again on SQL Server 2025. It also answers the model database question and shows the server-level shortcut.
Linked Server Logins: Stop Mapping Everyone to sa
Audit linked server logins for blanket remote sysadmin mappings, test with a low-privilege identity, and replace broad access safely.
Reading Connection Details in Code: APP_NAME, HOST_NAME and Logins
An audit row blamed the wrong machine because a label was treated as proof. Here is which connection values you can trust, and which you cannot.
Finding Databases Owned by Personal Logins and Fixing Them
Find databases owned by personal logins, review an approved replacement owner, and test dbo mapping and execution-context effects.