One of my friends was trying to configure database mirroring and was having a hard time in getting things working. The challenge was that he was using certificate for mirroring authentication because machines were workgroup not in domain. He followed one of the blog from Microsoft site but still having problems.
Life can teach you interesting lessons and push you beyond the boundary of what we call as a comfort zone. Recently I had a customer who was working on SQL server 2008 R2 and was enabling Mirroring. The very first thought was to recommend them to use AlwaysOn but that was not in their current scope because the application that they were working with was supported with SQL Server 2008 R2. The next thought for me was to understand what they were looking for as part of this consulting call. They incidentally wanted to enable Transparent Database Encryption (TDE) on their server and wanted me to guide on how to enable the same because the ISV had not done this before with a Database Mirroring configuration. So they were taking my help to understand how this needs to be systematically done with minimal downtime.
SQL SERVER – Mirroring Error 1412 – The remote copy of database has not been rolled forward to a point in time that is encompassed in the local copy of the database log. (Microsoft SQL Server, Error:)
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.
The best way I have learnt about building SQL Server AlwaysOn Availability Group is by contacting my close friends who have written the only book on this topic. It is not common that I ping them for such technical queries, but that is what friendship is made off. Recently, while preparing a demo for the AlwaysOn Availability Group, I ran into interesting issue and was able to fix it as well. Let us learn about the Database Mirroring login error.