Here I go again …..
So, I convince the powers that be that Simple Recovery Model is not such a great idea for Point in Time Recovery and they won’t have a choice if they want to go Always On Avail Groups which someday I actually hope to have a functional
system in place but I need the servers first, and that’s not the issue at hand.
We have a downtime schedule for day after tomorrow and Index Rebuild is # 1 on the list.
I have a couple of VM’s I can test with so I restore the latest copy of the one Database that will be included in that Maintenance Schedule.
Here is the size of the Data file:
115,668,992 KB
Log File Size:
28, 333, 632 KB.
So Off I go on my Index Rebuild and off the charts goes the Log File size;
Log File Size Before Index Rebuild:
28, 333, 632 KB
Log File Size After Index Rebuild:
89, 923, 584 KB
I have since changed to Simple Mode recovery and backed up, back to full and full back up followed by log backups and it’s still at the same size.
Given my limited by slowly growing SQL Server knowledge I have read more than once that Shrink File is not a good thing.
Any suggestions before this Maintenance Window is upon me and I have do to Index Rebuild against production?
R. Brown