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.
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.Â
SQL Authority News – Save USD 500 for SQL Live! 360 in November
I love talking about performance tuning and I love teaching about performance tuning. If you are in the USA, this is your opportunity to join me to discuss about SQL Server Performance. I’ll be speaking at Live! 360, November 12 – 17 in Orlando, FL. Live! 360 brings together five conferences, and the brightest minds in IT and Dev, to explore leading edge technologies and conquer current ones. More info:
SQL SERVER – How to Abort Index Rebuilding After Specific Time?
My favorite part of the SQL Server Performance Tuning Practical Workshop is the last part where we open up the floor for questions. Here is one question I received from a DBA last week about index rebuilding.Â
SQL SERVER – Automatic Startup Not Working for SQL Server Service
Sometimes some behaviors in SQL Server are unexpected and that’s the right time when an expert need to be engaged. In this blog post we will learn about how automatic startup sometimes does not work in SQL Server Services.Â
SQL SERVER – Find Out Column Name Using COL_NAME() Function
In SQL Server, there are many methods to find out the column names in a table. If you want to find out the column names based on the ordinal position you can do it querying system view size. Columns. Do you know that you can also do this by using COL_NAME() system function?
How is Oracle Temporary Table Different from SQL Server? – Interview Question of the Week #133
Question: How is Oracle Temporary Table Different from SQL Server?