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
Log backup for database “SQLAuthority” on secondary replica failed because the new backup information could not be committed on the primary database.
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.
SQL SERVER – Upgrade Error: The Server Principal is Not Able to Access the Database “msdb” Under the Current Security Context
The Upgrade Error messages shown in ERRORLOG was “The server principal “SQLAuthority\AuthOwner” is not able to access the database “msdb”
SQL SERVER – Fix: Logical Name Mismatch Between Catalog Views sys.master_files and sys.database_files
In this blog, I am going to share my learning about the mismatch between catalog views sys.master_files and sys.database_files.
SQL SERVER – Huge Space Used by Table sysxmitqueue in MSDB. How to Clear it Quickly?
Recently I was helping a customer who hired me for my services. He had an issue where they noticed that the size of the MSDB database has grown huge.
SQL SERVER – DBCC CLONEDATABASE Error – Msg 2601: Cannot Insert Duplicate Key Row in Object ‘sys.sysowners’ With Unique Index ‘nc1’.
A few days ago, I wrote a blog about an error while creating a clone of a database using DBCC CLONEDATABASE command. Here is the link to read that blog.