Find databases below the native compatibility level, generate reviewable ALTER statements, and prepare Query Store checks safely.
SQL SERVER – Script Level Upgrade for Database ‘master’ Failed Because Upgrade Step ‘msdb110_upgrade.sql’ Encountered Error 8649, State 1, Severity 17
Patching SQL 2017 failed at msdb110_upgrade.sql with error 8649: the query cost exceeded the configured threshold. Here is the cause and the fix.
SQL SERVER – Cannot Drop the Assembly ‘ISSERVER’, Because it Does not Exist or You do not Have Permission
An upgrade could not start SQL Server: Cannot drop the assembly ‘ISSERVER’, because it does not exist or you do not have permission. Here is another way to fix it.
SQL SERVER – Script level upgrade for database ‘master’ failed because upgrade step msdb110_upgrade.sql encountered error 926, state 1, severity 25
An upgrade failed: Script level upgrade for database ‘master’ failed because upgrade step msdb110_upgrade.sql encountered error 926. I explain the cause and the fix.
SQL SERVER – Upgrade Blocked: The Specified Edition Upgrade is Not Supported
Upgrading SQL Server 2008 R2 Express to SQL Server 2012 Evaluation failed with: Upgrade Blocked: The specified edition upgrade is not supported. Let me explain why.
How to Check Edition Specific Features Enabled In SQL Server? – Interview Question of the Week #180
Moving databases to another edition? Here is a simple script for SQL Server 2008 and later that lists the Edition specific features each database uses.
SQL SERVER – Upgrade Error – ALTER DATABASE Statement Not Allowed Within Multi-statement Transaction
A failed SQL Server 2014 SP2 left the service down with: ALTER DATABASE statement not allowed within Multi-statement Transaction. Here is how to fix it.