Dropped the database your logon trigger writes to? Every login then fails with Error 17892 Logon failed. I recreate the problem and show how to get back in.
Errors TRY CATCH Cannot Catch: Compile, Name and Severity Errors
Learn which errors TRY CATCH cannot catch, test execution scopes safely, and pair transaction cleanup with caller timeout handling.
SQL SERVER – Fix : Error : SQLDUMPER library failed initialization. Your installation is either corrupt or has been tampered with. Please uninstall then re-run setup to correct to correct this problem. in a modal dialog with the title SQL Writer
SQLDUMPER library failed initialization in a SQL Writer dialog does not mean you must reinstall SQL Server. Remove SQL Server VSS Writer and reboot.
SQL SERVER – FIX : ERROR : (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: )
Named Pipes Provider error 40, could not open a connection to SQL Server, hit me after I rebuilt my home network. Here are the common errors and the fix.
Restart History: Preserve Startup Evidence Before Logs Cycle
Restart history records startup evidence before retained logs disappear. Keep each source and timestamp separate, and test repeat collection with synthetic archives.
SQL SERVER – Fix : Management Studio Error : Saving Changes in not permitted. The changes you have made require the following tables to be dropped and re-created. You have either made changes to a table that can’t be re-created or enabled the option Prevent saving changes that require the table to be re-created
SSMS says saving changes is not permitted when a table must be re-created. Learn to turn off Prevent saving changes, and why I still prefer T-SQL.
SQL SERVER – FIX : Error: 18486 Login failed for user ‘sa’ because the account is currently locked out. The system administrator can unlock it. – Unlock SA Login
Error 18486 means the sa account is locked out, often after brute force attempts by hackers. Here is why it happens and how to unlock SA login.