The error which we observed was a failure of a rule – Patch Install Rule Error – Not clustered or the cluster service is up and online.
SQL SERVER – Historical PHYSICAL_ONLY Bug and Version Specific Evidence
A historical SQL Server 2017 Bug affected CHECKDB with PHYSICAL_ONLY and clustered columnstore data. One client observed a dump.
SQL SERVER – Upgrade Error: Microsoft NET Framework 4.0 Installation Has Failed With Exit Code – 2146498511
The solution of error Microsoft .NET Framework 4.0 installation has failed with exit code -2146498511 which was faced during SQL Server upgrade
SQL SERVER – Error 35296: Log Backup for Database “SQLAuthority” on Secondary Replica Failed Because the New Backup Information Could Not be Committed on Primary Database
Error 35296: log backup on a secondary replica failed because the new backup information could not be committed on primary. Here is the cause I found.
SQL SERVER 2019 – Installation Failure – Invalid Command Line Argument. Consult the Windows Installer SDK for Detailed Command Line Help
Invalid command-line argument. Consult the Windows Installer SDK for detailed command-line help. Let us see the error about Installation Failure.
msdb Upgrade Error 916: Fix the Database Owner
A msdb upgrade error can stop the service at the last upgrade step. The post reads the ERRORLOG, shows a read-only owner check, and walks through the four steps that fix the owner of msdb. The fix is one ALTER AUTHORIZATION statement.
Logical Name Mismatch: master_files vs database_files
A logical name mismatch means sys.master_files and sys.database_files disagree about a file name. A tested demo shows both views on one server, and a script checks every database. The post explains the secondary replica case and its fix.