With mirroring gone as deprecated feature, I have tried to keep away from exploring into what has been happening in this space. But what can I do when customers still use them? The challenges for consulting is pushing the boundaries of my comfort zone here. This made me revisit some of my learnings again. As part of this exercise, I learnt a minute or two which I personally felt was worth a share as part of this blog post. Here is a story for Mirroring Error 1412.
SQL SERVER – Installation Error – File Format is Not Valid
The reason I love consulting is because I get to see many flavors of the problems. This new avatar for me is pushing the limits to how I keep learning technologies. My recent interaction with client has shown one more error and another angle to look at a problem. Though some of these errors are new, it is a great way to understand how SQL Server actually works. In this blog post we will see Installation Error.
SQL SERVER – syspolicy_purge_history job failing step: Erase Phantom System Health Records
Getting back to consulting mode has got my newer clients and bigger challenges. Not only that I am seeing interests for some of the greatest and latest versions, but some clients are sitting on an older version of SQL Server requiring some serious help for trivial issues. One of my clients has asked to consult for a quick error message troubleshooting in the recent past. Since it was an interesting one about syspolicy_purge_history job, I am sharing it via the blog.
SQL SERVER – Setup Closed with Exit Code 0x80004005
Recently I was trying to help one of my clients to install Service Pack 3 for SQL Server 2008 R2 instance. Nothing was coming up when we were hitting setup.exe. I looked into my own blog and found Installation Log Summary File Location – 2012 – 2008 R2. But there was no file getting generated. I looked around of MSDN and found: https://docs.microsoft.com/en-us/sql/database-engine/install-windows/view-and-read-sql-server-setup-log-files?redirectedfrom=MSDN&view=sql-server-ver15. The reason was there was exit code 0x80004005.
SQL SERVER – Exception Code c0000005 While Starting SQL Service
Sometimes I get to see very weird errors by my blog readers and I have no clue about it. Getting a picture about what has happened in the past gives some hint about the solution. This post is a result of once such interaction, where we will see about Exception Code c0000005.
SQL SERVER – Unable to start SQL Server Agent – Failed to Initialize SQL Agent log
My friend was researching with SQL Agent parameters and after sometime he called me and told that he is not able to start SQL Agent service. Here was the error in SSMS which is about failed to initialize a SQL Agent log.
SQL SERVER – AlwaysOn Availability Group Stuck in Resolving State For Long time
What is resolving state in SQL Server AlwaysOn?
When there is an availability group, the replica would be either in primary state or secondary state – when its online in failover cluster manager. Resolving is an intermediate state when the transition is happening from primary to secondary or vice versa. If due to some reason the transition is not successful, it goes to “resolving” state. In this state, the database is not accessible.