Learning never stops for a consultant. In this blog, I would share another learning and discuss message: cannot shrink log file because the logical log file located at the end of the file is in use.
SQL SERVER – Cannot Shrink Log File Because Total Number of Logical Log Files
Since I wrote my article about the script of shrinking the Log Files, there have been many emails from my blog readers about various messages.
SQL SERVER – Information Message: Cannot shrink file in database to xxxx pages as it only contains yyyy pages.
I often get emails from my blog readers asking various types of clarifications about my own blog. Here is one of the interesting questions from a reader about message Cannot shrink file in the database to xxxx pages as it only contains yyyy pages which he encountered after following my below blog.
How to Shrink All the Log Files for SQL Server? – Interview Question of the Week #203
Question: How to Shrink All the Log Files for SQL Server?
SQL SERVER – Script – Transaction Log Backups Based on Growth / Size
While doing a comprehensive health check of the SQL Server, one of the things I check is the backup plan for the production databases. Many times, I have run into a situation where a customer says ” Transaction log file of the database has grown more than expected. I want to know the reason why and how to reclaim space and how to avoid such situations”. Let’s break it down into two parts and then
How to Shrink TempDB Without SQL Server Restart? – Interview Question of the Week #163
Question: How to Shrink TempDB Without SQL Server Restart?
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.