SQL SERVER – FIX: The Log for Database Cannot be Shrunk Until All Secondaries Have Moved Past the Point Where the Log was Added

While preparing for a demo for a client I was hit with an interesting error in AlwaysOn Availability Group backup and restore scenario. In my lab setup, I had four nodes SQLAUTH1 to SQLAUTH4 and I have always on high availability turned on SQL Server 2016. I played and did several operations with database and found that I have bloated the transaction log file to 100 GB. And now I need to shrink the transaction log on SQLAUTH1. As soon as I did that, I was welcomed with below message about database cannot be shrunk until all secondaries have moved past the point.

Read More

SQL SERVER – Caution: Adding Node in AlwaysOn Availability Group

It is interesting to see that in the past few days I have seen a similar pattern of an issue hit by three clients. All of them contacted me for a short engagement for the same issue. As you might know, every single day I keep two slots available for On Demand (50 minutes) so here is one of their emails. Let us learn about adding node in the AlwaysOn availability group. 

Read More

SQL SERVER – FIX: RequireKerberos Error During SQL 2008 Installation on Windows 2008 R2 Cluster

Today the progress made in technology is astounding and beyond our imaginations, but still there are clients who can’t move to higher, latest and greatest version of SQL so easily. They are still stuck with SQL 2005 and SQL 2008 SQL servers. In this blog post we will learn how to fix RequireKerberos Error During SQL 2008 Installation on Windows 2008 R2 Cluster.

Read More