However, the one thing that I tell SQL Server DBAs is that taking a logīackup, switching to SIMPLE recovery model or even detaching and re-attaching We can reclaim space from inactive VLFs when we shrink the database transaction log file. Take a log backup to truncate the log and mark the VLFs inactive so we can go ahead and shrink the log file. Rows with Status column value of 2, we can figure out which VLFs are in use (also called Active) or not (also called Inactive.)Īlso, in a previous tip on How to shrink the transaction log file in SQL Server, we've seen how we can The tip also tells us that, if we are to check the We have seen how we can use the undocumented command DBCC LOGINFO to get information about the virtual log files (VLFs) in our SQL Server databases. In a previous tip on How to determine SQL Server database transaction log usage, How do I know why I can't shrink my log fileĪnd what is the minimum possible size for me to shrink it? However, I still can't reclaim all the free space inside the To verify that I have more than 90% free space. I checked the log file free space and ran DBCC SQLPERF (LOGSPACE) I want to shrink the SQL Server transaction log file to reclaim disk space and reduce the number of virtual log files (VLFs) after I have scheduled regular Greg Robidoux and Jeremy Kadlec ( Co-Founders) Take 30 seconds to register for our newsletter and look for freeĮducational content to help you grow your career. Research new topics and solutions every day, but we can keep you informed. We know your day is hectic and you don't necessarily have time to New SQL Server content on a daily basis as well as offers free webinars Please do not scroll away - stay informed.ĭid you know that publishes
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |