Trying to figure out what I should do here. I was looking through our current Sharepoint server (SharePoint 2013, on-prem, this server is a VM and sits in our data center so it is backed up nightly full backup followed by weekly incremental. ) and found that there were no backups/maintenanceplans in place on SQL. One of the database transaction logs is insanelyhuge. A sharepoint_config transaction log is currently 634 GB. The database itself is only 1.4 GB. I don't know what the last people were doing when configuring this, but I want to fix this database as well as a few others that are over 150 GB each (those are actual data files, not transactionlogs). I have been reading up on how to truncate/shrink, but I am a bit confused on what to do. Obviously,the log should not be that big. I think I need to do either a full backup and then a...
↧