Opening a database diagram failed with error 15517: Cannot execute as the database principal because the principal ‘dbo’ does not exist. Let me show you the fix.
SQL SERVER – FIX: The specified instance of SQL Server is hosted by a system that is not a Windows Server Failover Cluster(WSFC) Node.
After a cluster rebuild, adding a replica failed: The specified instance is hosted by a system that is not a Windows Server Failover Cluster node. Here is the fix.
SQL SERVER – SQL Server Configuration Manager Missing from Start Menu
SQL Server Configuration Manager missing from the Start Menu? Open it directly from C:\Windows\System32 with the SQLServerManager msc file for your version.
SQL SERVER – SQL Service Not Getting Started Automatically After Server Reboot While Using gMSA Account
My first gMSA test: SQL Service was not started automatically after server reboot, even with automatic startup set. Here is what the event log showed.
SQL SERVER – Error: 18456, State 149 – Login-based Server Access Validation Failed With an Infrastructure Error. Login Lacks Connect Endpoint Permission
Connecting to the DAC with SQLCMD, I got Error 18456, State 149: Login lacks connect endpoint permission. Here is what the ERRORLOG showed and how to fix it.
Fix Error 3637: Backup Fails on a DAC Connection
To fix error 3637, find out why your backup runs on a dedicated administrator connection. This post reproduces the message with sqlcmd and its -A switch, shows the same backup working on a normal connection, and lists where a DAC hides in scripts and scheduled tasks.
ISSERVER Assembly Upgrade Error: Cannot Drop the Assembly (Msg 15151 and 6528)
An ISSERVER assembly error during a SQL Server upgrade needs the surrounding SSISDB messages before you choose a repair. The tests here trigger both errors in a throwaway database, show how they differ and run the catalog checks safely when SSISDB is missing or unreadable.